Skip to main content
Glama

readfetch

readfetch_probe

Read-only

FREE — no payment or wallet: Free preflight on a URL before any paid readfetch_* call: HTTP status, content type, byte size, title, language, and whether a bot wall is waiting (challenge). When the response is HTML and not a challenge page, the JSON includes preview: the text readfetch_text would return (same extractor), up to 32,000 characters for the first 3 probes per IP per day, then 400 characters. Use readfetch_probe instead of readfetch_text when choosing a route or estimating size; if challenge: true, use readfetch_scrape (then readfetch_residential if still blocked), not readfetch_text. Plain HTTP only — no browser render.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL to inspect.
timeout_sNoTotal budget for the whole call in seconds (default 10, max 60). Shared across redirects; does not apply to paid readfetch_text timeout_s on a follow-up call.
accept_languageNoAccept-Language header, e.g. 'de-DE,de;q=0.9'. Defaults to en-US.

Output Schema

NameRequiredDescriptionDefault
urlNo
bytesNo
titleNo
billedNo
statusNo
previewNo
languageNo
challengeNo
redirectedNo
status_codeNo
content_typeNo
requested_urlNo
content_sha256No

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 the cost model (free, no wallet), the quota mechanics (32,000 chars for the first 3 probes per IP per day, then 400), extractor parity with readfetch_text, and the hard constraint of plain HTTP with no browser render. These are exactly the traits that change how an agent plans a call and are unavailable from structured fields.

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?

Front-loads the 'FREE' qualifier and the core output list before the quota and fallback rules, and every clause carries actionable information. It is dense and relies on bold and parentheticals rather than clean sentence separation, which slightly hurts scanability but wastes no words.

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?

The tool has an output schema, so return values need no explanation, yet the description still flags the two fields that matter for planning (challenge and preview). Cost, quota, rendering limits, and the fallback path are all covered, leaving no gap an agent must guess at.

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%, including the shared-across-redirects note on timeout_s and the Accept-Language default, so the schema already carries parameter meaning. The description adds no per-parameter detail beyond restating the HTTP-only nature of the call; baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource (free preflight probe on a URL) plus the exact payload it returns: HTTP status, content type, byte size, title, language, challenge flag, and a text preview. It explicitly distinguishes itself from readfetch_text, readfetch_scrape, and readfetch_residential, so an agent can pick it 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?

Gives an explicit routing rule: use readfetch_probe instead of readfetch_text when choosing a route or estimating size, and if `challenge: true` fall through to readfetch_scrape then readfetch_residential. It names both the preferred alternative and the escalation chain, leaving nothing to inference.

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.