extract_batchExtract up to 10 freight documents in one call. Provide an array of fetchable URLs; each document is processed and billed independently, and the response reports a per-document outcome so partial success (e.g. running out of credits mid-batch) is explicit.
| Name | Required | Description | Default |
|---|---|---|---|
| urls | Yes | URLs of documents to fetch and extract (max 10) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses important behavioral traits beyond the annotations: each document is processed and billed independently, and the response reports per-document outcomes, making partial failures (e.g., running out of credits) explicit. This adds meaningful context about cost and partial success, complementing the annotations (readOnlyHint=false, openWorldHint=true). No contradictions noted.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded with the core purpose. Two sentences deliver all necessary information: the batch limit, the input format, independent billing, and the per-document outcome reporting. No word is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity (one param, no output schema), the description is remarkably complete. It covers the batch limit, the requirement for fetchable URLs, independent billing, and the explicit handling of partial success. This is sufficient for an agent to understand the tool's behavior and likely outcomes without an output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already has 100% coverage with a clear parameter description ('URLs of documents to fetch and extract (max 10)'). The tool description adds the semantic nuance that URLs must be 'fetchable' and that the batch is processed independently per document, which enriches the understanding of the parameter's role and constraints beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Extract up to 10 freight documents in one call.' It uses a specific verb ('extract') and resource ('freight documents'), and distinguishes itself from sibling tools like extract_bol (likely single extraction) and export_documents (export vs extract). The batch aspect is highlighted, making its purpose unique.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use this tool: when multiple documents need extraction in a single call. It explains the array of URLs and the per-document billing model. However, it does not explicitly name alternative tools for single-document extraction or state when NOT to use this tool, so it lacks explicit exclusions/alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action and resource: single extraction, batch extraction, document retrieval, listing, export, corrections, reconciliation, and account usage. extract_bol vs extract_batch is the only close pair, but single vs batch is a clear distinction.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: export_documents, extract_batch, extract_bol, get_document, get_related_documents, get_usage, list_documents, save_corrections. No mixed styles or vague verbs.
8 tools is well within the ideal 3-15 range. Each tool earns its place by covering a distinct step in the document processing workflow, with no redundancy or bloat.
The toolkit covers the full lifecycle: extraction (single and batch), retrieval (get/list), update (save_corrections), export, reconciliation, and account management. There are no obvious gaps that would hinder agent workflows.