Skip to main content
Glama

readfetch

readfetch_crawl

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. Start a bounded async crawl from one seed URL. Returns job_id, status (queued), pages_quoted, and price_usd — then poll readfetch_crawl_status with that id until status is complete or failed. A complete job includes per-page url and Markdown in the status payload. Cap scope with max_pages (default 20, max 100) and max_depth (default 2, max 3); include/exclude filter paths by prefix (* suffix on include). Prefer readfetch_batch for a fixed URL list; readfetch_map to list URLs without fetching bodies; readfetch_text for a single page.

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": {
      "url": "<url>"
    },
    "name": "readfetch_crawl"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesSeed URL; crawl stays on the same registrable domain.
excludeNoPath prefixes to skip during the crawl.
includeNoPath prefixes to allow; * suffix wildcard.
max_depthNoLink depth from the seed URL (default 2).
max_pagesNoMaximum pages to fetch in this job (quoted up front for payment).

Output Schema

NameRequiredDescriptionDefault
hintNo
job_idNo
statusNo
price_usdNo
pages_quotedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds material behavior the annotations cannot express: a funded Base USDC wallet is required, direct calls without a signing client terminate at 402, and the accepted auth paths (readfetch-client, @readfetch/client, @readfetch/mcp-x402-proxy) are named. It further discloses the async lifecycle (job_id, status=queued, pages_quoted, price_usd) and that completed jobs carry per-page url and Markdown in the status payload.

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?

Dense but purposeful, with no filler sentences and a clean progression from prerequisites to action to follow-up to alternatives. The main structural flaw is ordering: the payment preamble occupies the opening position that should belong to the purpose statement, delaying the one-line "what it does" until the second sentence.

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?

For a paid, asynchronous, open-world crawl tool, the description covers the prerequisite (funded wallet), failure mode (402), lifecycle and polling, and sibling routing. Return fields are also summarized even though an output schema exists, so an agent has everything needed to call, pay for, and complete the workflow.

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 all five parameters are already documented structurally, and the description largely restates what the schema says (max_pages default 20 / max 100, max_depth default 2 / max 3, include/exclude as prefix filters with * wildcard). The one genuinely additive note is that quoted page count drives up-front payment, but that is framed as billing behavior rather than parameter meaning, so the baseline 3 holds.

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?

"Start a bounded async crawl from one seed URL" gives a specific verb (start), resource (crawl), execution model (async) and scope constraint (bounded, one seed). It is immediately distinguishable from readfetch_text (single page), readfetch_map (URL listing only) and readfetch_batch (fixed list), which the description names directly.

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 rules: prefer readfetch_batch for a fixed URL list, readfetch_map to list URLs without fetching bodies, readfetch_text for a single page. It also gives the follow-up protocol — poll readfetch_crawl_status with the returned job_id until complete or failed — so the agent knows both when to enter and when to exit this workflow.

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.