Skip to main content
Glama

Tribute Paper

Fetch a page

fetch
Read-onlyIdempotent

The full text of one search result by its id, such as "design:garden-of-grace-funeral-service", "reading:psalm-23", "help:refunds", "policy:privacy", "faq:1" or "page:/pricing".

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 from search, e.g. reading:psalm-23.

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 behavior, so the safety profile is covered. The description's added value is the enumeration of id prefixes, which reveals the range of content types fetchable here (design, reading, help, policy, faq, page). It says nothing about truncation, size limits, or behavior for an unknown/malformed 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?

A single sentence fragment with no wasted words; the resource is front-loaded and the examples follow. It is slightly awkward as a fragment lacking an explicit verb, but nothing is padding.

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 one-parameter read tool with an output schema and full annotation coverage, the description supplies what the structured fields do not: the id taxonomy and the search-then-fetch relationship. Only the routing versus sibling retrieval tools is left unaddressed.

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 coverage is 100% and already documents the single id parameter with an example, so the baseline is 3. The description goes beyond it by showing six concrete id formats across different namespaces, which teaches the agent the id grammar that the schema only samples once.

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?

States a specific action and resource: returns the full text of exactly one search result, addressed by id. The id-namespace examples (design:, reading:, help:, policy:, faq:, page:) make the scope concrete. It stops short of differentiating itself from siblings like get_reading or get_design, so it lands at 4 rather than 5.

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: the phrase 'by its id' and the pointer to ids 'from search' suggest the intended search-then-fetch workflow. There is no explicit statement of when to prefer this over get_reading/get_design, and no exclusion conditions.

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