Skip to main content
Glama

readfetch

readfetch_diff

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. Stateless change detection on readable page text (same HTTP-first extraction as readfetch_text): fetch the URL, compare to a hash or prior body you store client-side, return changed/unchanged plus optional line diff. First call with no prior fields returns a baseline hash (see hint). previous_hash alone detects change without a line diff; add previous_content when you need added/removed/diff. A no-change answer is still billable when text was delivered. Prefer readfetch_text when you need the full article once; readfetch_probe (free) for a short preview and content_sha256 before spending on text.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) page to re-fetch and compare; must match the extraction used when you saved the hash (same `format`).
formatNoExtraction flavour for this fetch and for the hash (default text). Must match how you built `previous_content` if you send it.text
timeout_sNoTotal budget for the whole call in seconds, both fetches included. 60 s is the ceiling on this route.
previous_hashNo`sha256:…` or bare hex from readfetch_diff, readfetch_probe `content_sha256`, or a prior text read. Omit on the first poll to establish a baseline hash in the response.
previous_contentNoFull prior extracted text (what you stored from readfetch_text/readfetch_diff). Required for `added`/`removed`/`diff` output; hash-only compares do not emit a line diff.

Output Schema

NameRequiredDescriptionDefault
urlNo
diffNo
hashNo
hintNo
addedNo
billedNo
statusNo
changedNo
removedNo
status_codeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only say readOnlyHint and openWorldHint, so the description carries the cost model and does it well: it discloses that calls are paid, that a no-op still bills when text was delivered, that unsigned calls stop at 402, and that state is client-side so nothing is stored server-side. The only gap is that it doesn't say how long a baseline hash stays valid or what errors look like, but with an output schema present that omission is minor.

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 each sentence carries load; the billing and client requirement, the statelessness model, the parameter interaction, and the sibling routing are all necessary. Deducting one point because it opens with the payment/signing prerequisite rather than the tool's core purpose, so the key verb+resource is not front-loaded.

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 present, the description needn't explain return shapes, and it doesn't. What remains — prerequisites, cost behavior, baseline flow, parameter combinations, and alternatives — is fully covered, and all five parameters are documented in the schema, so an agent has everything needed to call this correctly on the first try.

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 goes beyond the per-field text by explaining the interaction between parameters: previous_hash alone yields a change boolean without a diff, while adding previous_content is required to get added/removed/diff, and format must match how prior content was built. That cross-parameter semantics is genuine added value.

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: "Stateless change detection on readable page text", and pins down the mechanism (fetch URL, compare to hash or prior content, return changed/unchanged plus optional diff). It explicitly distinguishes itself from readfetch_fetch, readfetch_text, and readfetch_probe, so an agent can route without opening a 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 explicit when-to-use and when-not-to-use guidance: "Prefer readfetch_text when you need the full article once; readfetch_probe (free) for a short preview and content_sha256 before spending on text." It also prescribes the first-call workflow (omit previous_hash to establish a baseline) and the hash-only vs hash+content choice.

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.