Skip to main content
Glama

fetch_documents

Download selected or all procurement documents (up to 300) through a durable local queue, with retry status and file/job size limits.

Instructions

Fetch selected stable document keys, or all (maximum 300), through the durable local queue.

    Hard limits: 200 MB per file, 1 GB per job. A queued retry reports its error and next_attempt.
    Read downloaded document IDs from list_documents(refresh=false). No import into a price catalogue.
    

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": {
      "source": "<source>",
      "number": "<number>"
    },
    "name": "fetch_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysNo
numberYes
sourceYes
enqueue_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real operational traits: per-file and per-job size limits, that work goes through a durable local queue, and that a queued retry surfaces its error and next_attempt. It still omits whether the call blocks or returns immediately, and any auth/permission requirements.

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 purpose, then limits, then retry behavior and follow-up in short declarative sentences with no filler. The stray indentation and line breaks are cosmetic noise rather than wasted content.

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?

An output schema exists, so return values need not be explained, and the description covers the queue mechanics and hard limits well. However, for a 4-parameter tool with zero schema documentation, the unexplained 'source' and 'number' parameters leave a real gap.

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

Parameters2/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 compensate. It clarifies 'keys' (selected stable document keys) and the default 'all, maximum 300', but leaves 'source' and the string-typed 'number' completely unexplained, and only obliquely hints at 'enqueue_only' via the queue wording.

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?

States a specific verb and resource (fetch documents) plus scope: either selected stable keys or all, capped at 300, delivered through a durable local queue. This is describable enough to separate from list_documents and read_document, though it never explicitly contrasts itself with those siblings.

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?

Gives a follow-up step ('Read downloaded document IDs from list_documents(refresh=false)') and one exclusion ('No import into a price catalogue'), which implies context. It does not say when to choose fetch_documents over read_document or list_documents, nor what prerequisites exist before queueing.

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