mcp-route-master

Open a route-master result

fetch

Read-onlyIdempotent

Open one search result by ID to retrieve its title, text, URL, and metadata as JSON. Use it with ChatGPT connectors and deep research to pull selected result content.

Instructions

Open one search result by id. Returns JSON {"id", "title", "text", "url", "metadata"}. Standard fetch tool for ChatGPT connectors and deep research.

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

Name	Required	Description	Default
`id`	Yes	An id returned by search.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Nov 5, 2026

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, non-destructive, and closed-world, so the safety profile needs no restating. The description adds value the annotations cannot: the exact return shape ({"id", "title", "text", "url", "metadata"}), which is important given there is no output schema. It stops short of covering invalid/expired id behavior or truncation of `text`.

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 short sentences, action first, return shape second — front-loaded and waste-free. The trailing "Standard fetch tool for ChatGPT connectors and deep research" is largely platform boilerplate that adds little for an agent choosing between siblings.

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 retrieval tool with no output schema, the description supplies the essential missing piece: the returned fields. What remains unstated (failure modes for unknown ids, payload size limits) is minor for a read-only idempotent fetch.

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 coverage is 100% and the sole parameter already documents "An id returned by search" with a maxLength. The description restates "by id" without adding format, source, or validity-window details, so the schema does the real work — baseline 3.

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?

"Open one search result by id" gives a specific verb (open/fetch) and resource (a single search result), and the field list makes the payload concrete. It implicitly separates itself from the sibling `search` (this retrieves one item by id), but it never names any sibling explicitly, including the adjacent `read_page`, so full differentiation is left to inference.

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 id is "returned by search", so an agent can infer this follows a search call. There is no explicit statement of when to prefer this over `read_page` or `page_action`, and no when-not guidance or error/precondition notes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server