Skip to main content
Glama

X420 agent services

x420_sitescan_business

Read-onlyIdempotent

SiteScan Business: Expanded multi-page audit with sitemap check and recommendations. Price: $7.00 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON report, up to 4 pages. Note: the local x420-mcp refuses this service above its default $1.00 per-call cap; set X420_MCP_MAX_USD=7 there to allow it.

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

Input Schema

NameRequiredDescriptionDefault
urlYespublic http(s) URL to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond annotations: annotations only mark it read-only, idempotent and open-world, but the description discloses the price ($7.00 USDC on Base), that this hosted endpoint does not pay and does not return the audit, exactly what the response contains (pay_to, network, price, x402 URL), and the $1.00 cap pitfall in the local server. The deliverable format (JSON report, up to 4 pages) is also disclosed. No contradiction with readOnlyHint/destructiveHint=false.

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?

Front-loads the key surprise first ('does NOT pay and does NOT return the deliverable'), then the payment procedure, then the cap caveat. Dense but each sentence carries actionable information. Slightly overpacked into one paragraph, but no filler.

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?

With no output schema, the description fully covers what a caller receives (payment instructions, then a JSON report up to 4 pages) and the complete payment protocol flow. The cap caveat anticipates the most likely operational failure. Nothing material to correct invocation is missing.

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 the single 'url' parameter is already documented as a public http(s) URL to audit. The description adds no further semantics for it (no scheme restrictions beyond http(s), no accessibility prerequisites). Baseline 3 is appropriate since the schema does all the work.

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?

Names a specific resource and scope: 'Expanded multi-page audit with sitemap check and recommendations'. The word 'Expanded' relative to the basic sibling is implied, but the description never names x420_sitescan_basic or x420_sitescan_check to make the distinction explicit. An agent can tell what it does, but must infer which sibling tier it is.

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?

Strong operational guidance: the tool does not produce the deliverable, GET the url, read PAYMENT-REQUIRED from the 402, retry with PAYMENT-SIGNATURE, or use the local x420-mcp server for automatic payment. It also warns that the local server refuses this service above its $1.00 default cap unless X420_MCP_MAX_USD=7 is set. It does not, however, state when to pick this over the basic or check siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources