Lordevo Shop (x402 website checks)

Page metadata + Markdown ($0.002/call)

page_meta

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Fetch and read the web] Read one public web page and return clean Markdown of the main content plus metadata: title, meta description, canonical, robots, lang, Open Graph/Twitter tags, headings outline, JSON-LD types, internal/external links, images missing alt, word count. Obeys robots.txt. ~1-3 s.

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

Input Schema

Name	Required	Description	Default
`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.

Output Schema

Name	Required	Description
`url`	No
`lang`	No
`tool`	No
`cache`	No
`links`	No
`title`	No
`_trial`	No	Present when the call was a free trial call.
`images`	No
`status`	No
`headings`	No
`markdown`	No
`provider`	No
`canonical`	No
`price_usd`	No
`word_count`	No
`json_ld_types`	No
`meta_description`	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"
+      ]
+    },
+    {
+      "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"
+    },
+    "canonical": {},
+    "headings": {
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "images": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "json_ld_types": {
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "lang": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "links": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "markdown": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "meta_description": {},
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "status": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "title": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tool": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "word_count": {
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive, so the safety profile is settled. The description adds genuinely new behavior: it obeys robots.txt, returns in ~1-3 s, and is metered at $0.002 per call with a 3-per-IP-per-UTC-day free trial. That pricing and latency disclosure is the kind of context annotations cannot express, though failure modes (blocked by robots.txt, non-200 pages, JS-only pages) are not described.

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?

Two sentences, front-loaded with the price signal that matters for a paid endpoint, followed by a bracketed purpose tag and then the payload. The long comma-separated field list is dense but each item is a distinct returned artifact; only the pricing sentence's parenthetical slightly duplicates the schema's trial description.

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?

An output schema exists, so the field enumeration is technically redundant, yet it usefully previews what an agent gets. Combined with robots.txt compliance, latency, and cost/trial mechanics, the definition covers everything needed to decide and call correctly. It stops short of 5 because error and edge-case behavior for non-HTML, blocked, or paywalled pages is unaddressed.

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 still adds meaning by explaining the trial mechanism ('add "trial": true or use try_free') and by implication that the URL must be public, which goes beyond the schema's dry type declarations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Read one public web page') and enumerates the payload: clean Markdown plus title, meta description, canonical, robots, lang, OG/Twitter tags, headings, JSON-LD types, links, images missing alt, word count. That clearly separates it from thin extractors, but it never names or contrasts with close siblings such as page_markdown, page_quality, or seo_page, leaving the agent to infer the boundary.

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?

Usage is only implied by the enumerated output fields: an agent can guess it is the right tool when it needs both readable content and on-page metadata in one call. There is no explicit when-to-use/when-not-to-use statement and no pointer to page_markdown (Markdown only) or seo_page (audit-oriented) as alternatives, so selection against siblings is left to inference.

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?