zFinia Intelligence

Page Fingerprint

page_fingerprint

Fetch a reviewed public page and return SHA-256 hashes of both the raw HTML and the visible text, with byte and character counts. Two hashes because they answer different questions: the HTML hash moves when anything at all changes, the text hash moves only when the content a reader would notice does. Pay 4000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

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": "page_fingerprint"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	HTTPS URL on a reviewed public origin. Permitted origins: https://docs.python.org, https://developer.mozilla.org, https://en.wikipedia.org, https://www.cisa.gov, https://www.sec.gov, https://home.treasury.gov, https://books.toscrape.com. robots.txt is honoured and redirects are refused.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the exact cost (4000 atomic USDC on Base via x402) and, crucially, that MCP does not pay but hands off a challenge. That is non-obvious behavior an agent must know before calling. It omits what the challenge handoff response contains and any caching or size-limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: what is returned, why two hashes exist, and how payment works. The core action is front-loaded and the payment caveat follows logically.

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?

With no output schema, the description must describe return values and does so (two hashes plus byte and character counts). Payment flow is covered at the policy level. The missing piece is the shape of the x402 challenge handoff that the agent must act on, which leaves a small gap for a paid tool.

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% and the single url parameter already documents the permitted origins, robots.txt handling, and redirect refusal. The description adds only the framing 'reviewed public page,' which reinforces but does not extend the schema. Baseline 3 applies 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?

The first sentence names a specific verb (Fetch) plus the resource (reviewed public page) and the exact return payload (SHA-256 of raw HTML and visible text, with byte/character counts). The dual-hash explanation further separates it from the other page_* siblings, which return rendered content or structure rather than hashes.

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 clear situational context: the HTML hash tracks any change while the text hash tracks reader-visible change, so an agent knows which value to compare for drift detection. It also states the payment prerequisite. It does not name alternatives such as batch_page_fingerprint for multi-URL work, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All zFinia Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?