Skip to main content
Glama

TraceVero

Read an entry with sources

fetch
Read-onlyIdempotent

Retrieve a public result from search. Every declared feature retains its source, collection date and explicit-empty indicator.

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

NameRequiredDescriptionDefault
idYes
localeNoen

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds output-oriented context (source, collection date, explicit-empty indicator), but says nothing about what happens when an id is unknown or inaccessible, and returns are already covered by the output 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?

Two short sentences, front-loaded with the action and resource. The second sentence is dense but informative; only the phrase 'explicit-empty indicator' is slightly opaque.

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?

Annotations and an output schema cover safety and return shape, so the remaining burden is modest. But for a fetch-by-id tool, the definition never says where a valid id comes from or how errors surface, leaving a real gap for an agent composing a call.

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% across two parameters, so the description must carry the burden and does not. The 'mcp/…' versus 'agenten/…' id forms and the meaning of the de/en locale are left entirely to the raw pattern and enum, with no explanation of which prefix corresponds to which record family.

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?

"Retrieve a public result from search" names a specific verb and resource, and the title/description make clear it is a read-by-id lookup that materializes one entry rather than a listing. It stops short of explicitly contrasting itself with the sibling search tool, which would have made the distinction airtight.

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?

Usage is only implied by the phrase 'from search', suggesting this is the detail step that follows a search hit. There is no explicit when-to-use/when-not statement, no instruction that the id must come from a prior search, and no alternatives named.

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