Tier 1 Protocol

Fetch exact Tier 1 span

fetch

Read-onlyIdempotent

Paid exact-span retrieval after Tier 1 search. Accept only an unchanged id returned by search for the same account. Authentication and an active paid plan are required. Do not invent ids, browse nearby text, or change files.

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 exact result id returned by a successful Tier 1 search for the same signed-in account. Never invent or alter this id.

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`text`	Yes
`title`	Yes
`metadata`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for adding things annotations cannot express: the paid-plan and authentication preconditions and the constraint that the span must be identical to an existing search result. It does not mention cost per call, rate limits, or failure modes for stale ids.

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?

Front-loaded with purpose in the first sentence, then constraints, then prohibitions — a sensible order with no filler. The closing 'or change files' clause is slightly tangential for a read-only fetch, but it is brief and reinforces the non-mutating contract.

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, fully-annotated, output-schema-backed tool, the description covers purpose, prerequisites, and id provenance adequately. The main loose end is that 'exact span' is never characterized (granularity, size, what gets returned), which an agent might need to use results correctly.

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% for the single id parameter, and the schema already states it must come from a successful Tier 1 search for the same signed-in account and must never be invented or altered. The description largely restates that contract rather than adding new syntax or format detail, so the baseline 3 applies.

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 (exact-span retrieval) and pins its position in the workflow ('after Tier 1 search'), which cleanly separates it from the sibling 'search' tool. The 'Paid' qualifier further distinguishes it from free-browse behavior.

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 explicit invocation conditions: only with an unchanged id returned by search for the same account, with authentication and an active paid plan. It also lists prohibitions (do not invent ids, browse nearby text, or change files), but it does not contrast against the other siblings render_context_results or authorize_sources.

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

All Tier 1 Protocol tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.