Lordevo Shop (x402 website checks)

Batch link check (up to 10 URLs per call) ($0.002/call)

links_batch

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Web and domain checks] The link-check for up to 10 URLs in one paid call (comma-separated): for each, alive or dead with the reason, final URL after redirects, redirect chain, cross-domain / HTTPS-downgrade flags, content type and TLS. robots.txt is checked before each URL and redirect is requested. ~1-6 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": {
      "urls": "<urls>"
    },
    "name": "links_batch"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	Yes	1-10 public http(s) URLs, comma-separated
`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
`dead`	No
`tool`	No
`alive`	No
`cache`	No
`count`	No
`_trial`	No	Present when the call was a free trial call.
`results`	No
`provider`	No
`price_usd`	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",
+        "count",
+        "results"
+      ]
+    },
+    {
+      "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"
+    },
+    "alive": {
+      "type": "integer"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "count": {
+      "type": "integer"
+    },
+    "dead": {
+      "type": "integer"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 26, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With annotations already covering readOnly, idempotent, openWorld and non-destructive, the description still earns credit for disclosing cost ($0.002 via x402/USDC on Base), the free-trial escape hatch, expected latency (~1-6 s), and the notable behavioral fact that robots.txt is checked and redirects are requested before each fetch. The enumeration of result fields (final URL, redirect chain, TLS, content type) is partly redundant because an output schema exists.

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?

The single paragraph is dense but the ordering is wrong: pricing and payment mechanics lead, while the actual purpose ('link-check for up to 10 URLs') arrives after a bracketed category tag. The price also duplicates the title and the trial mechanism duplicates the schema, so several clauses do not earn their place up front.

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?

For a paid, open-world batch fetcher, the definition covers cost, trial limits, latency, robots.txt compliance and per-URL result scope, which is most of what an agent needs before calling. Return-value detail is already handled by the output schema, so its presence here is surplus rather than a gap.

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 (urls, trial) are already documented in structured fields, and the description's 'comma-separated' and 'up to 10 URLs' restate rather than extend the schema. It adds no format examples, no guidance on mixing domains, and no behavior for what happens when more than 10 URLs are passed.

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 gives a specific verb and resource — 'link-check for up to 10 URLs in one paid call' — and the batch/quantity framing distinguishes it from the single-URL link_check sibling. It never names link_check explicitly, so an agent must infer the pairing from the quantity clause rather than being told.

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 'up to 10 URLs in one paid call (comma-separated)', which signals this is the multi-URL path, and try_free is named as an alternative for free calls. There is no explicit 'use link_check for a single URL' exclusion or statement of when the batch form is a bad choice.

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?