Lordevo Shop (x402 website checks)

Agent readiness / AI visibility score (GEO) ($0.002/call)

agent_readiness

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [SEO, security and site verdicts] Scores how visible and usable a site is for AI assistants and agents (0-100, grade A-F): robots.txt rules for AI search and training crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended...), noindex/noai, /llms.txt quality, schema.org JSON-LD, sitemap, title/description/canonical/lang, Open Graph, content readable without JavaScript, and agent discovery files (/.well-known/x402, MCP server card, A2A agent card, OpenAPI). Findings with fixes. Obeys robots.txt.

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": "agent_readiness"
  }
}

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
`meta`	No
`tool`	No
`cache`	No
`fixes`	No
`grade`	No
`score`	No
`_trial`	No	Present when the call was a free trial call.
`content`	No
`sitemap`	No
`summary`	No
`findings`	No
`llms_txt`	No
`provider`	No
`price_usd`	No
`categories`	No
`open_graph`	No
`ai_crawlers`	No
`agent_discovery`	No
`structured_data`	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",
+        "score",
+        "grade",
+        "findings"
+      ]
+    },
+    {
+      "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"
+    },
+    "agent_discovery": {
+      "properties": {
+        "agent_card": {
+          "type": "boolean"
+        },
+        "mcp": {
+          "type": "boolean"
+        },
+        "openapi": {
+          "type": "boolean"
+        },
+        "x402": {
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "ai_crawlers": {
+      "type": "object"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "categories": {
+      "type": "object"
+    },
+    "content": {
+      "type": "object"
+    },
+    "findings": {
+      "items": {
+        "properties": {
+          "fix": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "severity": {
+            "enum": [
+              "critical",
+              "high",
+              "medium",
+              "low",
+              "info"
+            ],
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "fixes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "grade": {
+      "enum": [
+        "A",
+        "B",
+        "C",
+        "D",
+        "F"
+      ],
+      "type": "string"
+    },
+    "llms_txt": {
+      "type": "object"
+    },
+    "meta": {
+      "type": "object"
+    },
+    "open_graph": {
+      "type": "object"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "score": {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "sitemap": {
+      "type": "object"
+    },
+    "structured_data": {
+      "type": "object"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "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, open-world, so the safety bar is low; the description still adds real context: per-call price (x402/USDC on Base), a free-trial path with its 3-per-IP-per-UTC-day quota, and the fact that it obeys robots.txt (implying some targets may be skipped or partially unscored). Output schema exists, so return format needn't be explained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Pricing is correctly front-loaded, but the bracketed tag "[SEO, security and site verdicts]" is ambiguous filler, and the subsequent list of checks is a long dense run-on. The content is relevant but not well-structured, and a reader has to parse a 30-word enumeration to find the core score definition.

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 return-value detail is unnecessary; the description covers cost, trial availability, scoring scale, and the check categories. It is nearly complete, missing only explicit routing guidance against the many overlapping siblings (seo_audit_lite, site_verdict, security_headers).

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 description coverage is 100%, so the schema already documents both url and trial, including the trial quota. The description's mention of "add trial: true or use try_free" restates the schema rather than adding format or edge-case detail, so baseline 3 applies.

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?

States a specific verb and resource: it scores a site's visibility and usability for AI assistants/agents on a 0-100, A-F scale, and enumerates the exact checks (robots.txt rules for GPTBot/ClaudeBot/etc., llms.txt, JSON-LD, agent discovery files). The GEO/AI-readiness framing clearly separates it from generic siblings like seo_audit_lite or page_meta.

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 implied by the criteria list (use this when you care about AI-crawler visibility), and pricing/free-trial mechanics tell the agent about cost-gating. However it never explicitly says when to pick this over seo_audit_lite, site_verdict, or security_headers, and gives no exclusions or prerequisites beyond 'Obeys robots.txt'.

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?