Skip to main content
Glama

batch

batch
Read-only

Run up to 10 primitive calls in one round trip for one x402 payment of $0.02 (= $0.0020 per call, below the priciest single-call route at $0.01). Each request names an endpoint (normalize, validate, extract, redact, classify, dedupe, diff, chunk, extract_custom, validate_json, slugify, hash) and its input; results return in request order. Single payment, no streaming. Larger rungs cost less per call: /v1/batch/50 ($0.075, $0.0015/call) and /v1/batch/100 ($0.100, $0.0010/call). $0.02 USDC per successful call (x402, client-paid); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "batch"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations it discloses payment mechanics (x402, client-paid, $0.02 USDC), that failed calls are not charged, ordering guarantees ("results return in request order"), and the absence of streaming. These are exactly the operational traits an agent cannot infer from annotations or an empty schema.

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?

Front-loaded with the core action and the batch-size cap, and dense with useful facts. The pricing is restated twice (total then per-call) and the larger-rung pricing is a parenthetical aside that slightly interrupts the flow, but nothing is wasted.

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

Completeness4/5

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

For a zero-parameter wrapper tool with no output schema, the description covers cost, cap, ordering, streaming, and failure charging — enough to invoke it correctly. The remaining gap is what happens on a partially invalid batch (per-item errors vs whole-batch rejection), which matters for a fan-out tool.

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

Parameters4/5

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

The input schema is an empty object, so the description carries the whole burden — and it does, explaining that each request item needs an `endpoint` plus its input, and enumerating all twelve valid endpoint values. What it lacks is any statement of the per-request envelope shape or the 10-item cap enforcement behavior.

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?

States a specific verb and resource ("Run up to 10 primitive calls in one round trip") and enumerates the twelve endpoints it can dispatch. It also explicitly distinguishes itself from the larger rung siblings /v1/batch/50 and /v1/batch/100, so an agent can pick the right tool without opening a schema.

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?

Gives a clear cost-based reason to choose this tool ("$0.0020 per call, below the priciest single-call route at $0.01") and names the alternative rungs with their per-call prices. It stops short of an explicit when-not-to-use rule (e.g. use primitives directly for a single call), but the tradeoff is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.