LLPRO Campus

Check whether a web page changed

page_watch_check

Read-onlyIdempotent

Did a public web page change? Send a URL (and the content_hash from your last check). Get back the hash of the page's visible text, whether it changed, the title, a short excerpt and when it was fetched. Free. Nothing is stored: keep the hash yourself and send it next time. Public http(s) pages only (ports 80 and 443), text types only, 1.5 MB cap. Limits: Fetches with the user agent 'Countersign/1.0 (independent checker; LLPRO)'. One GET per call. robots.txt is not read.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Public http(s) URL to check.
`previous_hash`	No	content_hash from your last check. Leave out on the first check.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: declares the service is stateless ('Nothing is stored'), discloses the user agent string, one GET per call, the 1.5 MB cap, text-only content types, port restrictions, and that robots.txt is not read. These are exactly the operational facts an agent needs before calling a fetch tool.

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-loaded with the decision question, then inputs, outputs, and limits in descending order of importance. The telegraphic fragment style is dense but mostly earns its place; 'Free.' and the limits clause are useful rather than padding, though a few sentences could be merged.

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?

No output schema exists, yet the description enumerates the return payload (hash of visible text, changed flag, title, excerpt, fetch time) and covers statelessness, size, content-type, and protocol limits. Nothing an agent needs to call it correctly or interpret the result 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 adds real value by explaining the previous_hash parameter as a state-carrying loop ('keep the hash yourself and send it next time') rather than just a pattern-constrained string. The url parameter is only characterized as 'public http(s)', which the description restates with the port and size constraints.

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?

Opens with a specific question form ('Did a public web page change?') and names the exact verb, resource, and mechanism (URL + previous content_hash in, current hash and changed flag out). It is clearly distinct from siblings that fetch or snapshot page content rather than diffing it.

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?

The workflow is spelled out: omit the hash on the first check, keep the returned hash yourself, and send it next time. It also states eligibility ('public http(s) pages only') which tells the agent when not to call it. It stops short of naming a sibling for the case where the caller wants the page text or a signed snapshot instead.

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

All LLPRO Campus 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?