Lordevo Shop (x402 website checks)

Structured data extractor (JSON-LD, microdata, RDFa) ($0.002/call)

structured_data

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [SEO, security and site verdicts] Extracts schema.org data from one page: every JSON-LD item (Product, Article, Organization, FAQPage, Event, Recipe and others) as parsed JSON with missing required / recommended properties, invalid JSON-LD blocks, microdata itemtypes and RDFa types. 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": "structured_data"
  }
}

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
`items`	No
`_trial`	No	Present when the call was a free trial call.
`issues`	No
`provider`	No
`price_usd`	No
`rdfa_types`	No
`json_ld_count`	No
`json_ld_types`	No
`microdata_types`	No
`invalid_json_ld_blocks`	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",
+        "json_ld_count",
+        "items"
+      ]
+    },
+    {
+      "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"
+    },
+    "invalid_json_ld_blocks": {
+      "type": "integer"
+    },
+    "issues": {
+      "type": "array"
+    },
+    "items": {
+      "type": "array"
+    },
+    "json_ld_count": {
+      "type": "integer"
+    },
+    "json_ld_types": {
+      "type": "array"
+    },
+    "microdata_types": {
+      "type": "array"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "rdfa_types": {
+      "type": "array"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 26, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds behavior they cannot express: cost ($0.002/call, x402 USDC on Base), the free-trial escape hatch via "trial": true or try_free, a 1-hour cache, and a ~0.3-2 s latency range. It also discloses what the response contains, including the diagnostic angles (missing required properties, invalid JSON-LD).

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 dense sentences, cost and trial terms front-loaded, then capability. Every clause carries information. Minor deductions: the bracketed tag "[SEO, security and site verdicts]" is ambiguous filler, and leading with price rather than capability slightly delays the selection signal.

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, return values need no explanation, and the description still covers cost, caching, latency, and extraction scope. It stops short of stating what is returned when a page has no structured data (empty result vs error) or how non-HTML pages are handled, which matters for an open-world fetch tool.

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 both parameters are already documented including the 3-per-IP-per-UTC-day trial limit. The description only reinforces the trial flag and implies the url is a single page; it adds no format or semantics beyond the schema, so the 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 ("Extracts") and a precise resource (schema.org data from one page), then enumerates the exact formats and item types covered: JSON-LD items with missing required/recommended properties, invalid JSON-LD blocks, microdata itemtypes, RDFa types. That scope is unmistakable against siblings such as page_meta, seo_page, or seo_audit_lite, so the agent can select it without opening the schema.

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 only implied: "from one page" signals single-URL scope, and the pricing/trial sentence hints at the free alternative. There is no explicit statement of when to prefer this over seo_page, page_meta, or site_verdict, and no exclusions for non-HTML or JS-rendered pages.

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?