Skip to main content
Glama

call_api_batch

Destructive

Runs multiple API calls sequentially in one round trip and enables later calls to reuse earlier return values via $result for chained operations.

Instructions

Run several API calls in order in one round trip. Each call is {"target", "method", "args"}. {"$result": i} (as target or anywhere in args) is the raw return value of call i (0-based), so calls can chain, e.g. target {"$result": 0} after a call that returned a timeline.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "calls": "<calls>"
    },
    "name": "call_api_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsYes
stop_on_errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is carried structurally. The description adds genuine behavioral context with sequential ordering and the $result chaining contract, but it never warns that a mid-batch failure can leave earlier calls' effects in place, nor how partial results are surfaced — meaningful gaps for a destructive batch executor.

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

Conciseness4/5

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

Three tight sentences with the core behavior front-loaded and the chaining example following logically. No filler; the only minor cost is that the example rides on the same sentence as the placeholder rule, making it slightly denser than necessary.

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

Completeness3/5

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

For a destructive, no-output-schema tool with two undocumented parameters, the description covers the call shape and chaining but omits the return structure (ordered result list?) and error semantics. The chaining contract is the hardest part and is explained well, which keeps this above a 2.

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 description coverage is 0%, so the description must carry the burden, and it does well for the required `calls` parameter by spelling out the {"target", "method", "args"} item shape and the {"$result": i} placeholder. However `stop_on_error` is never mentioned at all — its default, and whether disabling it yields partial results or raises, is left entirely undocumented.

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

Purpose4/5

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

The description opens with a specific verb and resource: 'Run several API calls in order in one round trip.' That distinguishes it from a single-call sibling by emphasizing batching and ordering. It stops short of naming call_api explicitly as the non-batch alternative, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is implied by 'several API calls in order in one round trip' — an agent can infer this is the multi-call path and that chaining is the reason to choose it. There is no explicit when-not guidance and no named alternative for the single-call case, so the guidance remains inference-based rather than stated.

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

Deploy Server

Other Tools