Skip to main content
Glama

Fetch a search result

fetch
Read-onlyIdempotent

Read a search result's full page: a restaurant's menu, dietary options, hours and events, or a destination's. Returns Markdown text with its citable url. Ids look like "venue:acme-bistro", "venue:acme-bistro:menu", "destination:los-cabos" or "listing:los-cabos:1234".

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 exactly as search returned it.

Output Schema

NameRequiredDescriptionDefault
idNo
urlNo
textNo
titleNo
reasonNo
sampleNo
statusYes
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by stating the return format is Markdown text with a citable url, which is not obvious from the annotations alone.

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?

The description is two tight sentences with the primary purpose front-loaded, followed immediately by the useful output format and id examples. Every sentence earns its place and nothing is redundant.

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?

The tool is simple (one required parameter), annotations cover safety, and an output schema exists, so the description does not need to explain return values in detail. It still provides the Markdown/citable-url return behavior and id formats, making it largely complete, though it could explicitly mention that the id must come from search.

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%, so the baseline would be 3, but the description adds meaningful id syntax examples like 'venue:acme-bistro', 'venue:acme-bistro:menu', and 'destination:los-cabos' that go beyond the schema's generic note. This helps an agent recognize and construct valid ids.

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?

The description uses a specific verb and resource: 'Read a search result's full page,' and illustrates exactly what that page can contain (menu, dietary options, hours, events, destination details). This clearly distinguishes it from the section-specific siblings such as venue_menu or destination_guide because it fetches the complete page rather than one section.

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?

The description implies when to use it by saying it reads a search result's full page, and the schema note says the id must be 'exactly as search returned it.' However, it does not explicitly name alternatives or state when not to use this tool instead of the many section-specific siblings.

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