> ## Documentation Index > Fetch the complete documentation index at: https://docs.anyreach.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get Custom Table Tool Schema > Every agent tool this table produces. Returns complete `ToolCall` blocks — parameter schema AND the actions that execute them — ready to drop into an agent config's `tools`. Generated, not hand-written per deal: that is the scaling win the declared schema buys. The pair derived from the declared schema comes first, then one tool per stored query that an agent could actually use. Both live in one response on purpose: this endpoint is what a caller reads to answer "what can an agent do with this table", and a second endpoint would let that answer be half right. A query that is broken, turned off or stale contributes nothing — handing an agent a tool the validator has stopped vouching for fails mid-call. ## OpenAPI ````yaml /openapi.json get /core/custom-data/tables/{name}/tool-schema openapi: 3.1.0 info: title: Anyreach API version: 1.0.0 description: >- REST API for the Anyreach platform. Every endpoint is scoped to one organization. Authenticate with a bearer token and, if your token can reach more than one organization, name the one you mean with the `X-Anyreach-Org` header. See [Authentication](https://docs.anyreach.ai/api-reference/authentication). This reference is generated from the running service, so the request and response shapes here are the ones the API actually enforces. servers: - url: https://api.anyreach.ai description: Production security: - bearerAuth: [] tags: - name: Agents description: >- Create and configure the agent that handles a conversation, and manage its versions. An agent's behaviour lives in a version; publishing a version is what puts it on the air. - name: Conversations description: >- Create, list, retrieve, and message conversations between your users and Anyreach agents. - name: Conversation attachments description: >- Upload files into a conversation and read them back. Uploads are two-step: presign, PUT to the returned URL, then mark the attachment complete. - name: Conversation events description: >- The ordered event stream behind a conversation — turns, tool calls, transfers, and status changes. - name: Knowledge bases description: >- A knowledge base (a `dataset` in the API) is a collection of embedded content an agent can retrieve from. - name: Knowledge base sources description: Attach and detach sources to a knowledge base. - name: Sources description: >- A source is a file or URL whose content is ingested, chunked, and embedded. - name: Phone numbers description: >- Buy, list, and release phone numbers, and point each one at the agent that should answer it. - name: Trunks description: >- SIP trunks for bringing your own carrier. A trunk carries calls between your carrier and Anyreach. - name: Inbound routing description: >- Rules that decide which agent answers an inbound call, evaluated before the call connects. - name: Agent assist description: >- Look up the live-assist context for a number so a human agent can see what the AI agent knows. - name: Human handoff description: >- Connections to the help desk a conversation escalates into, and the test endpoint that proves one works. - name: Email domains description: >- Register a sending domain and verify its DNS before an agent can send from it. - name: Email addresses description: >- The addresses on a verified domain, and the agent that handles mail arriving at each one. - name: Unsubscribes description: >- The suppression list. An address on this list is never emailed again until it is removed. - name: Web widgets description: >- The embeddable chat and voice widget: its appearance, its allowed domains, and the agent behind it. - name: Campaigns description: >- An outbound campaign dials a contact list with a given agent on a given schedule. Start, pause, and close control its lifecycle. - name: Campaign contacts description: >- The people a campaign dials. Contacts can be added while the campaign is running. - name: Campaign configurations description: >- Reusable dialing settings — calling windows, retry policy, timezone handling — that campaigns reference. - name: Campaign stats description: >- Per-campaign outcome counters, and the organization-wide cap on how many calls run at once. - name: Custom data description: >- Your own tables, queryable by an agent mid-conversation. Define a table, load rows, and expose read-only stored queries as agent tools. - name: Metrics description: >- The definitions an LLM judge scores a conversation against. Lint and preview a metric before you run it at scale. - name: Evaluations description: A scorecard binding a set of metrics to a population of conversations. - name: Evaluation runs description: >- One execution of an evaluation over a conversation set, and the results it produced. - name: Workflows description: >- Automations built from steps. A workflow is edited as a version and goes live when a version is published and set live. - name: Workflow triggers description: >- What starts a workflow — a schedule, a webhook, or a point in an agent conversation. Triggers are versioned alongside the workflow. - name: Workflow executions description: >- Run a workflow and read back what happened. Executions are synchronous by default; use the async endpoint for long-running work. - name: Workflow credentials description: >- Secrets a workflow step authenticates with. Values are write-only — they can be set and rotated, never read back. paths: /core/custom-data/tables/{name}/tool-schema: get: tags: - Custom data summary: Get Custom Table Tool Schema description: >- Every agent tool this table produces. Returns complete `ToolCall` blocks — parameter schema AND the actions that execute them — ready to drop into an agent config's `tools`. Generated, not hand-written per deal: that is the scaling win the declared schema buys. The pair derived from the declared schema comes first, then one tool per stored query that an agent could actually use. Both live in one response on purpose: this endpoint is what a caller reads to answer "what can an agent do with this table", and a second endpoint would let that answer be half right. A query that is broken, turned off or stale contributes nothing — handing an agent a tool the validator has stopped vouching for fails mid-call. operationId: getCustomTableToolSchema parameters: - name: name in: path required: true schema: type: string title: Name - name: limit in: query required: false schema: type: integer maximum: 50 minimum: 1 description: Default number of records the search tool returns default: 5 title: Limit description: Default number of records the search tool returns - name: x-anyreach-org in: header required: false schema: anyOf: - type: string - type: 'null' description: Organization ID for user PATs (pat_ prefix tokens) title: X-Anyreach-Org description: Organization ID for user PATs (pat_ prefix tokens) responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/ToolSchemaResponse' example: table: string key_property: string references: key: string tools: - {} '404': description: Not found '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' security: - HTTPBearer: [] components: schemas: ToolSchemaResponse: properties: table: type: string title: Table key_property: type: string title: Key Property references: additionalProperties: type: string type: object title: References tools: items: additionalProperties: true type: object type: array title: Tools type: object required: - table - key_property title: ToolSchemaResponse HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError securitySchemes: bearerAuth: type: http scheme: bearer description: Personal access token or organization API key. See Authentication. ````