Skip to main content
Glama

Fetch

fetch
Read-onlyIdempotent

Full text of a search result by its id (a trust center section such as "sec:privacy" or a document "doc:"), with title and source URL for citation. Ids look like "<trust_center>/sec:privacy" or "<trust_center>/doc:".

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
idYesResult id from search

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered in structured fields. The description adds two useful behavioral facts beyond that: results are workspace-scoped and the listing includes returned ids for follow-up retrieval. It says nothing about result volume or whether the listing is paginated, which is the main residual gap.

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 sentences, front-loaded with the enumeration behavior and followed immediately by the routing rule. No filler or restated title, though the second clause is slightly dense.

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?

An output schema and annotations carry the return shape and safety profile, so the description needn't explain those. However, for a list operation with an optional pagination parameter and no schema documentation for it, the omission of any paging guidance leaves the definition incomplete relative to its complexity.

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?

The single parameter, cursor (pagination), has no description in the schema, and the description does not mention pagination, cursors, or how to page through results at all. The phrase 'Workspace-scoped' clarifies scope but does not explain the one input the agent actually has to supply.

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 ('Lists all available documents in the workspace, including both guides and reference APIs') and explicitly distinguishes the shape of what it returns from an id-based retrieval sibling. An agent can tell it apart from get_item without opening either schema.

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?

Gives a clear when-to-use condition ('discover the full set of resources available') and names the alternative with the condition that selects it ('if you already want a specific resource, prefer the get_item tool'). No explicit exclusions or caveats about large result sets, so it falls short of the top band.

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