Skip to main content
Glama

td_tool_batch

Dispatch up to 8 tool calls in a single roundtrip, reducing latency. Each call runs sequentially, with failures isolated per call.

Instructions

Dispatch up to 8 tool calls in one model roundtrip.

Each sub-call's result is returned in a structured array — per-call failures don't abort siblings. Use this for read-only sweeps ("inspect 5 things at once") to save model-to-server-to-model latency.

Hard constraints:

  • Maximum 8 sub-calls per invocation.

  • Nested td_tool_batch calls are rejected per-sub-call (fork-bomb guard).

  • Sub-calls execute sequentially (TD's Python API is not thread-safe).

Returns: {"ok": True, "count": int, "results": [ {"tool": str, "ok": bool, "result": dict|None, "error": str|None, "elapsed_ms": int}, ... ]}

``error`` is always ``str | None`` — dict errors from
``format_tool_error`` are normalised to their ``message`` field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
callsYesList of {tool: str, args: dict} dicts. Max 8 sub-calls.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses key behaviors beyond annotations: per-call failures don't abort siblings, sequential execution due to API non-thread-safety, and nesting rejection. Annotations provide no contradictory signals.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with bullet constraints and a clear return format. Every sentence adds value; no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description fully specifies the return structure including error handling. Covers all important aspects of a complex batch tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters with description of the 'calls' field. Description adds no new semantic meaning beyond what the schema already provides; baseline score applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Dispatch up to 8 tool calls in one model roundtrip' and explains the benefit of latency saving. It distinguishes this meta-tool from specific operational siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly suggests use for 'read-only sweeps' to save latency, and lists hard constraints (max 8 sub-calls, no nesting). Could be more explicit about when not to use, but the guidance is strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dreamrec/TDPilot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server