Skip to main content
Glama

Fetch a search result

fetch
Read-onlyIdempotent

Fetch a result using its exact typed ID from search. Tasks and Docs include body content, messages include bounded text, and files return metadata. A legacy bare ID is treated as a task. Requires the read permission for that source.

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
idYesExact result ID returned by search, including its type prefix. A bare ID refers to a task.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Existing task ID returned by list_tasks or search. Do not invent IDs."New value: +"Exact result ID returned by search, including its type prefix. A bare ID refers to a task."
    • removedInput schema / properties / id / maxLength
      Removed value: -100
    • removedInput schema / properties / id / minLength
      Removed value: -1
    • changedInput schema / properties / id / pattern
      Previous value: -"^[A-Za-z0-9_-]+$"New value: +"^(?:(task|doc|file|message):)?[A-Za-z0-9_-]{1,100}$"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond them: the payload shape per source (tasks/docs include body content, messages bounded text, files metadata) and the read-permission prerequisite for the source.

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?

Three short sentences, front-loaded with the action and ID requirement, then payload expectations, then the permission prerequisite. Every sentence carries information; no filler.

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?

An output schema exists, so return values need not be specified, yet the description still usefully summarizes per-type payload granularity and the permission gate. It stops short of describing failure behavior for an unknown, expired or cross-source ID, which would be the last missing piece for a single-parameter 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 description coverage is 100% and the schema already documents the type prefix and the bare-ID-means-task fallback, so the description largely restates it. The only marginal addition is the emphasis that the ID must be the exact one returned by search, which slightly narrows what a valid input is.

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 verb and resource ('Fetch a result') and constrains it to IDs produced by search, with typed prefixes for task/doc/file/message. That is far more specific than a bare 'fetch', though it never explicitly contrasts itself with the obvious siblings get_task or get_doc.

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: you use this when you hold an exact typed ID from search, and a bare ID falls back to task. There is no explicit when-not guidance or naming of alternatives such as get_task/get_doc, so an agent must infer the routing decision.

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.