Lordevo Shop (x402 website checks)

Canonical, hreflang and indexability check ($0.002/call)

canonical_check

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [SEO, security and site verdicts] Is this URL indexable and which URL is canonical: canonical tag or HTTP Link header, self-referencing or pointing elsewhere, multiple/relative/cross-domain canonicals, og:url mismatch, meta robots and X-Robots-Tag (noindex/nofollow), hreflang list with code validation, x-default and self-reference. Cached 1 h. ~0.3-2 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": "canonical_check"
  }
}

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
`tool`	No
`cache`	No
`_trial`	No	Present when the call was a free trial call.
`issues`	No
`hreflang`	No
`provider`	No
`canonical`	No
`indexable`	No
`price_usd`	No
`self_referencing`	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",
+        "indexable",
+        "issues"
+      ]
+    },
+    {
+      "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": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "hreflang": {
+      "type": "array"
+    },
+    "indexable": {
+      "enum": [
+        "indexable",
+        "noindex",
+        "canonicalised_elsewhere"
+      ],
+      "type": "string"
+    },
+    "issues": {
+      "type": "array"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "self_referencing": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "tool": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral context: cost per call with the x402/USDC payment rail, the free-trial mechanics, a 1-hour cache, and a ~0.3-2 s latency window - none of which is inferable from annotations.

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?

Pricing is front-loaded, then the domain label, then the substantive capability list. The dense comma-separated enumeration of checks is information-rich but borders on a run-on sentence; still, nearly every clause carries content.

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?

For a single-URL read-only diagnostic with an output schema and full annotation coverage, the definition supplies the checks performed, cost, caching and latency - everything an agent needs to decide to call it and interpret scope.

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% for both parameters, so the schema already defines 'url' and 'trial'. The description adds only the pricing/trial context ('trial': true or use try_free), which mildly reinforces the schema but adds no syntax or format detail beyond it. Baseline 3 applies.

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+resource framing ('Is this URL indexable and which URL is canonical') and enumerates the exact facets checked (canonical tag vs Link header, robots directives, hreflang), which distinguishes it from vague siblings like seo_page or page_meta. It stops short of naming a sibling it replaces, so a 4 rather than a 5.

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 checks: an agent can infer this is the canonicalization/indexability diagnostic, but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as seo_audit_lite or site_verdict.

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?