Skip to main content
Glama

readfetch

readfetch_fetch

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. Send an HTTP request (GET, POST, PUT, PATCH, DELETE, HEAD) through egress and return status_code, response headers, and body as text or base64 (binary: true). max_bytes caps the stored body; follow_redirects (default true) and timeout_s (95 s ceiling) apply to the full redirect chain. Use json_body for JSON POST/PUT payloads; use body for raw bytes or strings. Prefer readfetch_text for readable HTML articles; readfetch_pdf to extract PDF text (not raw bytes alone). POST/PUT/DELETE can change remote state despite readOnlyHint.

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

Input Schema

NameRequiredDescriptionDefault
urlYesRequest URL (http or https).
bodyNoRaw request body string for POST/PUT/PATCH (mutually exclusive with json_body).
binaryNoWhen true, return body as base64 instead of UTF-8 text.
methodNoHTTP method (GET default).GET
headersNoOptional request headers, e.g. Authorization or Accept.
json_bodyNoJSON object serialized as the request body (Content-Type application/json).
max_bytesNoStop reading and truncate once the response body exceeds this size (bytes).
timeout_sNoTotal budget for the whole call in seconds, redirect hops included.
follow_redirectsNoFollow 3xx redirects (default true).

Output Schema

NameRequiredDescriptionDefault
urlNo
sizeNo
textNo
billedNo
statusNo
status_codeNo
content_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only supply readOnlyHint=true and openWorldHint=true, and the description adds substantial behavior the agent could not infer: a paid route requiring a funded Base USDC wallet, the 402 stop condition, the required signing client/proxy, redirect-chain timeout semantics, and max_bytes truncation. It also explicitly warns that POST/PUT/DELETE can mutate remote state despite readOnlyHint, which corrects a potentially misleading annotation rather than contradicting it. This is exactly the extra context the behavioral dimension is meant to reward.

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 and essentially waste-free: every sentence carries either a precondition, a parameter hint, or a sibling routing rule, appropriate for a 9-parameter tool. The weakness is ordering — the core 'send an HTTP request' statement arrives after two sentences of wallet/proxy prerequisites, so the front-loaded element is setup friction rather than the tool's action.

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 general-purpose egress fetch tool with 9 parameters, a full schema, and an output schema, the description covers the critical unknowns: payment/auth prerequisites, the 402 failure mode, mutation risk on non-GET methods, and sibling routing. Return values are briefly summarized even though the output schema carries them. Minor gaps remain around rate limits, header restrictions, and egress/geo behavior, but nothing an agent needs to invoke the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still earns above baseline by giving selection guidance between the two overlapping body parameters ('use json_body for JSON POST/PUT payloads; use body for raw bytes or strings'). It also frames timeout_s and follow_redirects as applying to the full redirect chain and binary:true as a base64 switch, reinforcing the practical effect of each parameter. It adds meaning but does not fully document headers or the 2083-char URL limit, which the schema already covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: send an HTTP request across all six methods through egress and return status_code, response headers, and body. It also distinguishes itself from two siblings (readfetch_text for readable HTML articles, readfetch_pdf for PDF text), so an agent can route correctly. The main statement of purpose is buried behind two sentences of payment/setup preamble, which slightly blunts the front-loading.

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?

It gives explicit routing advice: prefer readfetch_text for readable HTML articles and readfetch_pdf for PDF extraction rather than raw bytes. It also tells the agent that direct calls without a signing client will stop at 402, which is actionable context for when a call will fail. It stops short of naming when a completely different sibling (e.g. readfetch_scrape or readfetch_crawl) is preferable over a raw fetch.

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.