Tool publication and presentation limits
Tool publication limits cap each Source at 4,096 Tools and bound each Agent Identity by total Tool size rather than count.
Tool limits for Sources, Agent Identities, and model presentation, including per-Source ceilings, size bounds, and the presentation budget.
- A Source publishes up to 4,096 Tools, bounded by a 4 MiB SDK registration payload.
- Agent Identity Tools are bounded by total size, roughly 15,000 small or 2,800 large.
- Duale AI presents roughly ten to sixty Tools directly and makes the rest searchable.
- Limits are split between versioned API contract and release settings that a release can change.
- Tool Call arguments, call rates, and remote server quotas fall outside these limits.
Summaries were generated by AI.
One Source publishes up to 4,096 Tools. One Agent Identity holds every Tool its Sources publish, bounded by their total size rather than by a count. Duale AI presents part of that set to the model and makes the rest searchable.
These limits stop one Source from crowding out the rest. None of them is per-seat or per-plan.
Some limits are part of the versioned API contract. Changing them breaks clients. Other limits are settings that a release can change.
- Class
- Versioned API contract
- Limits
- SDK registration Tool count and payload size, and the Tool Schema ceilings
- Class
- Release setting
- Limits
- MCP catalog check ceilings, the per-Agent Tool ceiling, and the presentation budget
How many Tools one Source can publish
A Source is one SDK Tool Host or one named MCP Connection, and both carry the same Tool ceiling.
- Limit
- Tools per Source
- Value
- 4,096
- Your action
- Split a larger catalog across Sources. Two MCP Connections to the same server stay independent.
- Limit
- SDK registration payload
- Value
- 4 MiB for the request as sent
- Your action
- The request travels compressed, so the Tool count binds first unless nearly every schema sits at its 16 KiB ceiling.
- Limit
- One SDK Tool’s input schema
- Value
- 16 KiB
- Your action
- Keep parameter descriptions short; they are for the model, not for your API reference.
- Limit
- One MCP Tool definition
- Value
- 512 KiB
- Your action
- Set by the remote server. Nothing on your side changes it.
- Limit
- MCP complete catalog check
- Value
- 30 seconds, 128 pages, 4 MiB
- Your action
- A server that paginates in very small pages can stop short of 4,096 Tools.
Tools reference states the remaining per-Connection MCP boundaries: schema depth, node counts, and Tool Result ceilings.
A publication that breaks a limit fails as a whole and changes nothing. An SDK registration answers 422 with
TOO_MANY_TOOLS, or 413 with REQUEST_BODY_TOO_LARGE when the request itself is too large. Tools already published
stay offered until the Tool Host stops sending heartbeats. An MCP catalog check fails, retries, and shows the failure in
the Connection’s catalog state rather than dropping Tools silently.
Operations explains reading that state.
How many Tools one Agent Identity can hold
Nothing caps the Sources you assign to an Agent Identity. An Agent Identity’s Tools are bounded by their total size rather than by a count, and the instructions for that model turn count against the same total.
That bound is roughly 15,000 small Tools, 7,000 mid-sized ones, or 2,800 large ones. A small Tool takes three parameters and a short description; a large one takes ten parameters and a 1,000-character description.
- Limit
- Sources per Agent Identity
- Value
- No ceiling
- Your action
- Assign by what the Agent Identity does, not by a count.
- Limit
- Tools per Agent Identity
- Value
- Bounded by total size
- Your action
- Nothing to configure. Split across Agent Identities only past the bound.
To see what one Agent Identity holds now and what it lost recently, open it in Agent settings and select
Tools. Read the same list through GET /tenants/{tenant_id}/agents/{agent_id}/tools; the Tools
reference states its filters and paging. The
organization Tools page counts Tools per Source instead.
Over that ceiling, Duale AI retries the model turn rather than run it without your Tools. Retrying does not shrink
the catalog, so the Task stops progressing and ends at its deadline instead of reporting the cause. Recognize it by a Task
that reaches TASK_DEADLINE_EXCEEDED with no Tool Call recorded, on an Agent Identity whose assigned Tools grew. Remove
a Source assignment to bring it back under the ceiling.
How Duale AI presents Tools to the model
Duale AI gives the model the Tools that fit a fixed budget, and a search over the rest.
- Presented directly: roughly ten to sixty Tools, depending on schema size.
- Reachable by search: every other Tool the Agent Identity holds. The model finds them by describing what it needs.
Duale AI does not rank the catalog by relevance today. It fills the budget in the order the catalog returns Tools, so a Tool presented first is not one the work is more likely to need.
Give an Agent Identity the Tools its job needs, not every Tool your organization publishes. A Tool past the budget costs the model a search step before it can call anything, and a broad Tool set gives it more near-matches to choose between. Split the work across Agent Identities when one Agent Identity’s job spans unrelated systems.
What these limits do not cover
- Tool Call arguments and results. These belong to the call, not the catalog. Tools reference states them for an MCP Tool, Authoring tools for an SDK Tool.
- Rate of calls. Nothing here limits how often an Agent Identity calls a Tool.
- Agent Identities per MCP Connection. Tools reference states that ceiling.
- The remote server’s own limits. An MCP server applies its own quotas to the access context your Connection uses, and Duale AI does not see them. A Tool that a server rate-limits fails as a Tool Result.