Lordevo Shop (x402 website checks)

Page change check: content hash, clean text and line diff ($0.002/call)

page_diff

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Fetch and read the web] Fetches one public page and returns a SHA-256 hash of its main text plus the clean text; if you send the previous hash or text it also says changed yes/no and, with previous text, lists added and removed lines. Input: url, optional previous_hash or previous_text. Limits: 1.5 MB page, 100,000 characters of text returned; robots.txt obeyed. Not cached.

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

Input Schema

Name	Required	Description
`url`	Yes	Public http(s) URL or bare domain, e.g. https://example.com
`trial`	No	Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms.
`previous_hash`	No	content_sha256 from your previous call
`previous_text`	No	text from your previous call (gives the changed lines; POST for long text)

Output Schema

Name	Required	Description
`url`	No
`diff`	No
`text`	No
`tool`	No
`cache`	No
`_trial`	No	Present when the call was a free trial call.
`status`	No
`changed`	No
`provider`	No
`price_usd`	No
`compared_with`	No
`content_sha256`	No
`text_truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / trial / description

Previous value: -"Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms."New value: +"Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms."

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / trial

Added value: +{
+  "description": "Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms.",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "required": [
+        "tool",
+        "url",
+        "content_sha256",
+        "text"
+      ]
+    },
+    {
+      "properties": {
+        "accepts": {
+          "type": "array"
+        },
+        "error": {
+          "type": "string"
+        },
+        "resource": {
+          "type": "object"
+        },
+        "x402Version": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "x402Version",
+        "accepts"
+      ]
+    },
+    {
+      "properties": {
+        "charged": {
+          "type": "boolean"
+        },
+        "error": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "_trial": {
+      "description": "Present when the call was a free trial call.",
+      "type": "object"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "changed": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "compared_with": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "content_sha256": {
+      "type": "string"
+    },
+    "diff": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "status": {
+      "type": "integer"
+    },
+    "text": {
+      "type": "string"
+    },
+    "text_truncated": {
+      "type": "boolean"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedNov 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, and the description adds real value on top: price and payment rail (x402 USDC on Base, trial flag), a 1.5 MB page cap, 100,000 characters returned, robots.txt obeyed, and that results are not cached. The main omission is how 'main text' is extracted, which affects hash stability across calls.

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 front-loaded with no filler sentences; every clause carries information (price, action, inputs, limits). The ordering is slightly off for tool selection—pricing and trial lead before the purpose, which appears bracketed in the second position.

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, return shape needn't be described, and the description still covers cost, limits, robots behavior, and both operating modes. An agent has everything needed to decide and invoke correctly.

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 slightly further by mapping modes to parameters ('with previous text, lists added and removed lines') and noting previous_text unlocks line-level output while previous_hash only yields a boolean. It omits 'trial' from its input summary, but that parameter is fully documented in the schema.

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?

Specific verb and resource: fetches one public page, returns a SHA-256 hash of its main text plus clean text, and optionally reports changed yes/no with added/removed lines. That combination of hash-plus-diff over a live URL separates it from text_diff (arbitrary text) and page_markdown (content extraction) even though siblings aren't named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the conditional behavior ('if you send the previous hash or text') so an agent can infer two modes: snapshot vs. change-check. But it never states when to pick this over text_diff for already-held text or page_markdown for full extraction, and gives no exclusions.

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

All Lordevo Shop (x402 website checks) 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?