Lordevo Shop (x402 website checks)

URL cleaner: strip tracking parameters, normalise, dedupe (up to 50) ($0.002/call)

url_clean

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Data utilities] Normalises up to 50 URLs offline: lowercases scheme and host, drops default ports, fragments, credentials and known tracking parameters (utm_*, gclid, fbclid, msclkid and similar), then removes duplicates; reports what changed per URL. Input: urls separated by spaces or new lines (or a JSON array via POST). No URL is fetched.

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

Input Schema

Name	Required	Description	Default
`urls`	Yes	1-50 http(s) URLs separated by spaces or new lines (or a JSON array in a POST body)
`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
`tool`	No
`cache`	No
`_trial`	No	Present when the call was a free trial call.
`unique`	No
`results`	No
`count_in`	No
`provider`	No
`price_usd`	No
`count_valid`	No
`count_unique`	No
`duplicates_removed`	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",
+        "unique",
+        "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"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "count_in": {
+      "type": "integer"
+    },
+    "count_unique": {
+      "type": "integer"
+    },
+    "count_valid": {
+      "type": "integer"
+    },
+    "duplicates_removed": {
+      "type": "integer"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "results": {
+      "type": "array"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "unique": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedNov 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered upstream. The description still adds real value beyond that: per-call pricing and payment rail, the free-trial mechanism with a per-IP daily cap, the 50-URL ceiling, and the fact that it reports what changed per URL.

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?

It is front-loaded with the price and then the core transform in one dense sentence, so an agent can stop reading early and still act. The '[Data utilities]' category tag and the repeated pricing from the title are mild filler, but nothing is genuinely wasted.

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 two-parameter, read-only transform tool with a 100%-covered schema and an output schema, the description covers everything an agent needs: the batch limit, accepted input encodings, what normalisation entails, what is stripped, that duplicates are removed, that nothing is fetched, and the cost/trial terms.

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, and the description largely restates the same input-format rules (space or newline separated, JSON array via POST). The trial flag's behaviour is described in the schema itself, so the description adds little semantic detail the agent could not read from the structured fields.

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?

The description states a specific verb and resource: normalise up to 50 URLs offline by lowercasing scheme/host, dropping default ports, fragments, credentials and tracking parameters, then deduping. That is concrete enough for an agent to distinguish it from siblings like canonical_check, url_trust or link_check without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is clear: this is an offline transform applied to a batch of already-known URLs, and the line 'No URL is fetched' implicitly rules out the fetching/liveness siblings. It also names the trial path ('trial': true or try_free) as an alternative for free invocation, though it never explicitly names a competing conversion tool to prefer or avoid.

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?