Skip to main content
Glama

Fetch (ChatGPT)

fetch
Read-onlyIdempotent

Texte intégral d'une section de programme à partir de son id (renvoyé par search).

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

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only that the payload is the complete, unabridged text rather than an excerpt, which is a modest but real behavioral detail; it says nothing about error behavior 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with the resource front-loaded and the id provenance trailing in parentheses; there is no filler. It is slightly clipped as a verbless fragment, but nothing needs to be removed.

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-only, non-destructive fetch with full annotation coverage and no output schema, the description gives the essential facts: what comes back (full text) and where the required id comes from. Only failure-mode behavior for invalid ids is left unstated.

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

Parameters4/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 carry the single parameter, and it does: it explains that 'id' identifies a program section and that ids originate from 'search', which is meaning not present in the bare string/maxLength=40 schema. The only remaining gap is any note on the accepted id format or length.

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?

The description names a specific resource and scope: the full text ('Texte intégral') of a program section, addressed by its id. It is clearly a retrieval-by-id tool and even attributes the id's origin to 'search', but it does not articulate how it differs from sibling readers such as lire_section, so an agent must infer that distinction.

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 implied rather than stated: the parenthetical '(renvoyé par search)' tells the agent that this tool is the retrieval step following a search, which is a useful chaining hint. However, there is no explicit when-to-use vs when-not guidance and no named alternative for cases where a summary or a different reader would be appropriate.

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.