Lordevo Shop (x402 website checks)

Page quality verdict (AI) ($0.005/call)

page_quality

Read-onlyIdempotent

$0.005 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [SEO, security and site verdicts] AI verdict on one page's content quality: high/medium/low with a 0-100 score, topic, strengths, problems and one-line summary, blended with measured metrics (word count, Flesch readability, headings, duplicate sentences, link ratio, author/date). Runs on Lordevo's own local model (no cloud AI). Obeys robots.txt. ~3-20 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_quality"
  }
}

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
`ai`	No
`url`	No
`tool`	No
`cache`	No
`topic`	No
`_trial`	No	Present when the call was a free trial call.
`metrics`	No
`summary`	No
`verdict`	No
`ai_score`	No
`problems`	No
`provider`	No
`price_usd`	No
`strengths`	No
`rule_score`	No
`quality_score`	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"
+    },
+    "ai": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "ai_score": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "cache": {
+      "type": "object"
+    },
+    "metrics": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "problems": {
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "provider": {
+      "type": "string"
+    },
+    "quality_score": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "rule_score": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "strengths": {
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "summary": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tool": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "topic": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "verdict": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), and the description adds genuinely useful behavior: per-call pricing, trial limits (3 per IP per UTC day), local-model execution with no cloud AI, robots.txt compliance, and a 3-20s latency band. The main gap is it doesn't say what happens when robots.txt blocks the page or the fetch fails.

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 well-organized: pricing and trial mechanism first, then a bracketed scope tag, then the verdict content and operational traits. Every sentence carries information, though leading with price is slightly suboptimal for selection over capability.

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 an output schema present and full parameter coverage, the description covers capability, cost, latency, and compliance sufficiently for an agent to decide and call. Only edge-case behavior (robots block, fetch failure, retry after trial exhaustion) is unspecified.

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%, so both parameters are already documented with expectations for url and trial. The description restates the trial pricing semantics but adds no syntax or format detail beyond what the schema provides; baseline 3 is appropriate.

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 names a specific verb and resource ('AI verdict on one page's content quality') and enumerates the verdict shape (high/medium/low, 0-100 score, topic, strengths, problems, summary) blended with measured metrics. It is distinguishable from siblings like readability or seo_page, though the bracketed tag '[SEO, security and site verdicts]' is noisy and could be confused with site_verdict or security_scan_lite.

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 context is implied (analyze a single page for content quality) but there is no explicit when-to-use/when-not guidance versus readability, seo_page or site_verdict. The only routing offered is a pricing alternative (try_free / trial:true), which helps with cost but not tool selection.

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?