Reecopedia

Read original evidence

fetch

Read-onlyIdempotent

Fetch original text by an opaque id from search or document_outline. Pass ids unchanged. Navigation containers have citable=false and child ids, not source evidence. Historical page identifiers return migration guidance.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 17, 2026

removedInput schema / properties / id / description

Removed value: -"A result id from `search`, format \"<source-file>#p<page>\"\n(e.g. \"REG_2024_1781_ESPR_EN.pdf#p39\")."

First observedJul 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds behavioral context beyond that: ids are opaque, must be passed unchanged, navigation containers have citable=false and child ids rather than source evidence, and historical page identifiers yield migration guidance. This meaningfully informs the agent about edge-case behavior without contradicting any annotation.

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?

Three tight sentences, each earning its place: the first states the core action and source, the second gives the critical pass-through instruction, and the third covers two edge cases. It is front-loaded and free of filler.

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

Completeness5/5

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

With only one parameter, an existing output schema, and annotations covering safety/idempotency, the description covers all essential operational details: id origin, pass-through requirement, container distinction, and historical-id behavior. Nothing needed for correct invocation is missing.

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

Parameters5/5

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

Schema description coverage is 0% and the schema only says 'id' is a string. The description fully compensates by specifying the id is opaque, originates from search or document_outline, must be passed unchanged, and clarifying which id types do not correspond to source evidence. This gives the agent a complete mental model of the single parameter.

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?

The description states a precise verb-resource pair: 'Fetch original text by an opaque id from search or document_outline.' It clearly defines the input source (ids from two named tools) and contrasts with navigation containers, making it distinguishable from siblings like search and document_outline.

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?

The description gives explicit guidance on what ids to pass: ids from search or document_outline, unchanged, and warns that navigation containers are not source evidence. It also notes that historical page identifiers yield migration guidance, which implicitly tells the agent not to expect source text for those. It lacks an explicit 'when not to use' statement naming alternatives, but the constraints are concrete and actionable.

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

All Reecopedia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?