Skip to main content
Glama

FIDES Ecosystem Explorer

fetch

Read-onlyIdempotent

Fetch the full record for a single FIDES catalog item by the result id returned from the search tool. Returns the document with a canonical URL for citation.

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
idYesA result id returned by search, e.g. 'wallet:org:animo::paradym'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds return-value context the structured fields don't provide — that the result is a document including a canonical URL suitable for citation — which helps an agent know the payload is citable output rather than a summary.

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?

Two sentences, zero filler, with the core action front-loaded and the required id provenance stated immediately after. Nothing is redundant with the name or annotations.

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

Completeness4/5

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

For a single-parameter read tool with rich annotations, this covers purpose, input provenance, and output shape well enough to call it correctly. The only omission is behavior on an unknown or malformed id (error vs. empty result).

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already documents `id` with a concrete example ('wallet:org:animo::paradym'), so the description adds little beyond reinforcing the provenance of the id. Baseline 3 is appropriate where the schema carries the parameter detail.

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?

States a specific verb and resource: 'Fetch the full record for a single FIDES catalog item by the result id.' It clearly distinguishes itself from the search siblings by being a single-record lookup keyed on an id produced elsewhere.

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?

Explicitly tells the agent the id must come from the `search` tool, which establishes the search-then-fetch workflow rather than leaving ordering to inference. It stops short of saying what to do when the id is unknown or invalid, so no explicit exclusion or failure path is given.

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