---
title: "Get Custom Table Tool Schema"
method: GET
path: "/core/custom-data/tables/{name}/tool-schema"
tags: ["custom_data"]
---

# Get Custom Table Tool Schema

`GET /core/custom-data/tables/{name}/tool-schema`

## Request

- Base URL: `https://api.anyreach.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.anyreach.ai/core/custom-data/tables/{name}/tool-schema`
- Auth: HTTP bearer

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.

## Path parameters

- `name` string, required

## Query parameters

- `limit` integer: Default number of records the search tool returns

## Headers

- `x-anyreach-org` string, nullable: Organization ID for user PATs (pat_ prefix tokens)

## Response `200`

Successful Response

- ToolSchemaResponse
  - `table` string, required
  - `key_property` string, required
  - `references` object
  - `tools` object[]

## Other responses

- `404`: Not found
- `422`: Validation Error

---

[API](https://skmtc.dev/anyreach/apis/anyreach-api.md) - [All operations](https://skmtc.dev/anyreach/apis/anyreach-api/llms.txt) - [OpenAPI document](https://skmtc.dev/anyreach/apis/anyreach-api/revisions/2eddf40c8c93?raw)