Skip to main content
Glama

Fetch (ChatGPT-style)

fetch
Read-onlyIdempotent

Get the full text for an id returned by search: an episode's summary and facts, a transcript passage with context, or a topic's facts.

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
idYesAn id returned by search, such as episode:acquired/nvidia-part-iii or topic:openai

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 covered. The description adds real value by disclosing that this single tool dispatches polymorphically: episode ids yield summary and facts, transcript ids yield a passage with context, topic ids yield facts. It does not say what happens for an unknown or expired id.

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?

One sentence, front-loaded with the verb and the constraint ('for an id returned by search'), followed by the payload variants. No filler or repetition of the schema.

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?

With a full output schema, complete annotations, and a single fully documented parameter, the remaining burden is small and the description carries what it needs to: source of the id and the shape of each result kind. Only error/edge behavior is left uncovered, a minor gap for a read-only lookup.

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 coverage is 100% and the schema already supplies the prefix examples ('episode:acquired/nvidia-part-iii', 'topic:openai'), so the description cannot add much. It does at least tie each id prefix to the kind of payload returned, which is meaning slightly beyond the schema's format hint. Baseline 3 is appropriate.

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?

A specific verb ('Get the full text') and resource ('an id returned by search'), plus an enumeration of the three id kinds the tool resolves: episode, transcript passage, topic. It's clear what the tool does, though it never contrasts itself with the overlapping siblings get_episode, get_topic, and get_transcript.

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?

'For an id returned by search' implies the search-then-fetch workflow, which is useful routing context. But there is no explicit when-to-use-this-vs-alternative guidance despite siblings that appear to serve the same per-entity retrieval, so selection still requires inference.

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