@readfetch/mcp-x402-proxy

readfetch_search

Read-only

Search the web without a separate search API subscription and return titles, URLs, and snippets so you can pick a result, then fetch its full page with a follow-up URL tool.

Instructions

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.

Input Schema

Name	Required	Description
`tbs`	No	Optional recency filter: h=hour, d=day, w=week, m=month, y=year.
`lang`	No	Optional language/locale hint, e.g. en or de-DE.
`limit`	No	Maximum number of results to return (default 5).
`query`	Yes	Search query string.

Output Schema

Name	Required	Description	Default
`hint`	No
`query`	No
`billed`	No
`status`	No
`results`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.1.13Nov 1, 2026

changedInput schema / properties / lang / description

Previous value: -"e.g. en, de-DE"New value: +"Optional language/locale hint, e.g. en or de-DE."

addedInput schema / properties / limit / description

Added value: +"Maximum number of results to return (default 5)."

addedInput schema / properties / query / description
```
Added value: +"Search query string."
```

changedInput schema / properties / tbs / description

Previous value: -"Time range."New value: +"Optional recency filter: h=hour, d=day, w=week, m=month, y=year."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "billed": {
+      "type": "boolean"
+    },
+    "hint": {
+      "type": "null"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "properties": {
+          "position": {
+            "type": "integer"
+          },
+          "snippet": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0Nov 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover read-only and open-world behavior, and the description adds genuinely useful context beyond them: no separate search API subscription is required, results are limited to titles/URLs/snippets rather than page text, and follow-up tools are required for full content. It also documents the recency filter semantics and result limit behavior.

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?

The description is front-loaded with the core action and output limitation, then provides usage routing. It is generally efficient, but some parameter detail duplicates the schema and could be trimmed without losing necessary guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, annotations, and full schema coverage, the description supplies everything an agent needs: purpose, output scope, parameter behavior, and sibling-tool routing. Nothing critical is missing for correct invocation.

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 description coverage is 100%, so parameter meanings are already fully documented in the schema. The description restates limit, lang, and tbs semantics, which is helpful but largely redundant; it adds examples for lang and expands tbs values, but does not add meaning beyond the structured fields.

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 states a specific verb and resource: run a web search. It immediately distinguishes this from full-page retrieval tools by saying it returns titles, URLs, and snippets only, not full page text.

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?

It explicitly routes the agent: follow with readfetch_text, readfetch_probe, or readfetch_scrape on a chosen URL. It also names alternatives for known-site tasks (readfetch_map/readfetch_crawl) and link-based tasks (readfetch_* URL tools), so when-to-use and when-to-use-something-else are clear.

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

Deploy Server