Skip to main content
Glama

QDev

Fetch a search result

fetch
Read-onlyIdempotent

The full text of one search result, by its id: an event written out with its dates, place, deadlines and links, or a page or post as markdown.

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 (event:<id>, page:<path>, post:<slug>).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 earns credit by disclosing the return shape, which no output schema provides: events are written out with dates, place, deadlines and links, while pages/posts come back as markdown. It does not state what happens for a missing or stale id, a minor gap.

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?

A single sentence, front-loaded with the core action, with the qualifying detail about output forms following in a natural clause. No redundant restatement of the title and 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?

For a one-parameter read tool with no output schema, the description supplies the key missing piece: what the returned payload looks like per id type. Absent is any note on error behavior or size/truncation limits, but that is minor at this complexity.

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 the schema already documents the event:/page:/post: id prefixes, setting a baseline of 3. The description adds real meaning beyond that by mapping each id type to the content form returned, which helps the agent predict the result before calling.

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 verb+resource: retrieve the full text of one search result by its id. It also enumerates the two result shapes (an event expanded with dates, place, deadlines and links, or a page/post rendered as markdown), so an agent knows exactly what comes back. It does not explicitly contrast with get_event/get_document, leaving mild ambiguity about which sibling fetches what.

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 through 'one search result, by its id', which tells the agent this follows a search call. There is no explicit when-to-use/when-not guidance or pointer to get_event/get_document as alternatives for direct id access.

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