Skip to main content
Glama

X420 agent services

x420_sitescan_basic

Read-onlyIdempotent

SiteScan Basic: Technical summary of a public website including robots.txt review. Price: $3.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.

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_basic"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYespublic http(s) URL to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only declare read-only, idempotent, open-world and non-destructive traits. The description adds the critical non-obvious behavior: this hosted tool does not pay and does not return the deliverable, it validates input and returns payment instructions, then spells out the 402 / PAYMENT-REQUIRED / PAYMENT-SIGNATURE retry flow. That is exactly the behavioral context an agent needs and cannot get from the annotations.

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?

The description is dense but front-loaded: deliverable, price, hosting caveat, payment procedure, alternative, and final output are each stated once. The payment-handshake sentence is unavoidably technical but every clause carries operational meaning, leaving little waste.

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 payment-gated hosted tool with a single fully documented parameter, the description covers the essential oddities (no deliverable without payment, the exact x402 retry flow, and the local-server alternative). It could be slightly more specific about what the 'technical summary' contains, but nothing required to invoke it correctly 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% and the single 'url' parameter is already documented as a public http(s) URL. The description repeats 'public website' without adding format, restriction, or validation 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete deliverable (a technical summary of a public website including robots.txt review) and its output format (JSON report), so the agent knows what the tool produces. It is somewhat differentiated by the 'Basic' tier label, but it never states how it differs from siblings like x420_sitescan_business or x420_sitescan_check.

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?

The description gives detailed guidance on the payment path (hosted x402 handshake vs. running the local x420-mcp server with a wallet key), which is genuinely useful. However, it offers no guidance on when to choose this Basic tier over the sibling business/check variants, which is the main selection decision an agent faces.

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