Skip to main content
Glama

readfetch

readfetch_map

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. Discover a site's crawlable surface without crawling it: parse robots.txt allow/disallow rules, collect URLs from sitemap.xml and sitemap indexes, find RSS, Atom and JSON feeds, and count internal and external links on the homepage. Use the returned URLs to plan readfetch_scrape, readfetch_batch, or readfetch_crawl — not readfetch_map again on each URL. Prefer readfetch_probe on one URL before paying for bodies.

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_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL of the site to map.
limitNoMaximum number of URLs to return (1-1000).
max_bytesNoAbort if any single document exceeds this many bytes.
timeout_sNoTotal budget for the whole call in seconds; every sitemap fetch and the browser fallback share it. 95 s is the edge ceiling (Cloudflare closes at 100 s).

Output Schema

NameRequiredDescriptionDefault
urlNo
hostNo
urlsNo
feedsNo
linksNo
billedNo
robotsNo
statusNo
sitemapsNo
url_countNo
status_codeNo
total_foundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the monetization model: a funded Base USDC wallet is required on paid routes, a signing client or @readfetch/mcp-x402-proxy is needed, and unsigned direct calls fail at 402. It also notes the 95 s edge ceiling and that the browser fallback shares the timeout budget. It stops short of describing failure modes for unreachable sites or how robots/documents errors surface, so not a 5.

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 purpose sentence is dense but front-loaded with the core capability, and the workflow/alternative instructions follow logically. The opening payment/wallet preamble consumes the highest-attention position before the tool's function is stated, which costs a point.

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 read-only, open-world, four-parameter tool with full schema coverage and a declared output schema, the description supplies everything an agent still needs: payment/auth prerequisites, the 402 failure condition, the timeout ceiling, what is returned, and which sibling to call next. No material gap remains.

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 four parameters (url, limit, max_bytes, timeout_s) are already documented with defaults and bounds. The description adds no parameter-level meaning of its own and does not explain how limit interacts with the collected sitemap/feed URL pool, so 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 precise verb and resource: "Discover a site's crawlable surface without crawling it", then enumerates the exact artifacts produced (robots.txt rules, sitemap URLs, RSS/Atom/JSON feeds, link counts). The negation "without crawling it" and the instruction not to re-run readfetch_map on each returned URL cleanly separate it from readfetch_crawl.

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 downstream routing: use returned URLs to plan readfetch_scrape, readfetch_batch, or readfetch_crawl. Also gives a pre-condition alternative ("Prefer readfetch_probe on one URL before paying for bodies") and an anti-pattern (do not call readfetch_map per URL), so both when-to-use and when-not-to-use are covered.

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.