Skip to main content
Glama

X420 agent services

x420_sitescan_check

Read-onlyIdempotent

SiteScan API check: Machine-readable technical checks of one public page: security headers, SEO basics, accessibility signals, performance indicators. Price: $0.50 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 with score, grade, findings.

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

Input Schema

NameRequiredDescriptionDefault
urlYespublic http(s) URL to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered; the description nonetheless adds the critical behavior nobody would guess, that this tool does NOT pay and does NOT return the deliverable. It also discloses the exact price ($0.50 USDC per call on Base), the x402 protocol handshake, and what the paid deliverable contains (JSON report with score, grade, findings), which is exactly the context an agent needs before calling.

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 capability and the price are front-loaded, and the crucial caveat (does not pay, does not return deliverable) follows immediately. The payment-mechanics sentences are dense and read as a run-on, mixing GET/402/PAYMENT-SIGNATURE steps into prose, but almost every sentence carries necessary operational information.

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, single-parameter, no-output-schema tool, the description covers scope, price, protocol flow, alternate local route, and the shape of the paid deliverable, so an agent can complete the call correctly. The remaining gap is tier selection against the basic and business siblings, which the description never addresses.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single parameter at 100% schema description coverage, the schema already defines url. The description still adds scope semantics, that the target must be a public page and only one page is audited per call, which prevents an agent from passing authenticated or multi-page targets. That is modest but genuine added meaning.

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?

Starts with a specific verb and resource: "Machine-readable technical checks of one public page: security headers, SEO basics, accessibility signals, performance indicators," which is far more informative than the name. It does not, however, distinguish this tier from the sibling tiers x420_sitescan_basic and x420_sitescan_business, so an agent cannot tell from the description alone which scan level it is buying.

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?

Gives explicit operating instructions: this hosted tool validates input only, then the agent must GET the url, read PAYMENT-REQUIRED from the 402, and retry with PAYMENT-SIGNATURE, or alternatively run the local x420-mcp server with its own wallet. That is strong when-to-use and how-to-use coverage. It does not state when to pick this over the basic or business scan tiers, which is the one missing selection rule.

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