Skip to main content
Glama

readfetch

readfetch_search

Read-only

Paid routes require a funded Base USDC wallet. Use readfetch-client / @readfetch/client or the MCP signing proxy (@readfetch/mcp-x402-proxy). Direct calls without a signing client will stop at 402. Run a web search without a separate search API subscription. Returns titles, URLs, and snippets only — not full page text; follow with readfetch_text, readfetch_probe, or readfetch_scrape on a chosen result URL. limit is 1–20 (default 5). Optional lang biases locale (e.g. en, de-DE). Optional tbs filters recency: h= past hour, d= day, w= week, m= month, y= year. Use readfetch_map/readfetch_crawl when you already know the site; readfetch_* URL tools when you have the link.

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": {
      "query": "<query>"
    },
    "name": "readfetch_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
tbsNoOptional recency filter: h=hour, d=day, w=week, m=month, y=year.
langNoOptional language/locale hint, e.g. en or de-DE.
limitNoMaximum number of results to return (default 5).
queryYesSearch query string.

Output Schema

NameRequiredDescriptionDefault
hintNo
queryNo
billedNo
statusNo
resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the supplied readOnlyHint/openWorldHint annotations: it discloses the paid-route prerequisite (funded Base USDC wallet), the required signing client/proxy, and the concrete failure mode (calls stop at 402 without one). It also caps expectations on the payload (snippets only, not page text), which shapes downstream planning.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense and each clause is relevant, but front-loading is inverted: the first two sentences are payment/proxy logistics rather than the tool's action, and the final paragraph compresses parameter details, alternatives, and multi-tool routing into one long run-on block. It could be restructured to lead with what the tool does and push payment prerequisites later.

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?

With an output schema present, the return shape need not be spelled out, and the description still usefully summarizes it. Auth/payment requirements, failure mode, and successor-tool routing are all covered; only cost/latency or rate-limit expectations are left unstated for a paid, open-world call.

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%, so the schema already documents query, limit, lang and tbs. The description restates the same facts (limit 1–20 default 5, tbs h/d/w/m/y, lang locale examples) without adding format rules, interaction notes, or edge cases beyond what the structured fields carry.

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+resource ("Run a web search") and immediately bounds the output scope ("titles, URLs, and snippets only — not full page text"), which is exactly what separates it from the readfetch_scrape/text siblings. An agent can identify this as the discovery step without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: follow with readfetch_text/probe/scrape on a chosen URL, use readfetch_map/crawl when the site is already known, and use readfetch_* URL tools when a link exists. It names both the successor tools and the conditions that select them, so no inference is required.

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.