Skip to main content
Glama

Extract batch

extract_batch

Run up to 20 extract calls. Each item has its own status. Call extractors.list for the sample schema. Call keys.create once. Pass caller_key on every later tools/call.

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": {
      "items": "<items>"
    },
    "name": "extract_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
caller_keyNopf_ key from keys.create. Pass this on tools/call when Authorization and X-Caller-Key are not set. A header key wins if both are set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / caller_key
      Added value: +{
      +  "description": "pf_ key from keys.create. Pass this on tools/call when Authorization and X-Caller-Key are not set. A header key wins if both are set.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds genuinely non-obvious behavior — per-item independent status (partial failure is possible) and an auth handshake requiring a pf_ key from keys.create with header precedence. It stops short of saying what the status values mean or what happens to failed items.

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?

Four telegraphic sentences, the batch scope front-loaded and each remaining sentence carrying a distinct operational instruction. No filler or restated title text.

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?

With no output schema, the description should describe the response shape; it only says each item has its own status, leaving the status vocabulary, result payload, and failure/retry behavior unstated. The auth workflow is complete, but the return contract for a 20-item batch is thin.

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?

Schema coverage is 50% and the two item fields (url, json_schema) carry no descriptions, so the description must compensate: it does so by capping items at 20 and pointing to extractors.list for the json_schema sample. caller_key semantics live in the schema already and the description only echoes the placement rule.

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?

"Run up to 20 extract calls" states a specific verb (run extracts) plus the batching scope and hard cap, which distinguishes it from the single-item extract sibling. It does not spell out what an "extract call" produces (URL + json_schema → structured output), so it leans on prior knowledge of the sibling.

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?

It gives concrete orchestration prerequisites (call extractors.list for the sample schema, call keys.create once, pass caller_key on later tools/call), which is real when-to-use guidance. It never says when to prefer extract over extract_batch or when not to batch, so the alternative-selection guidance is only implied by the item cap.

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.

Resources