Skip to main content
Glama

x420_sitescan_check

Run a paid technical audit of one public URL for security headers, SEO basics, accessibility, and performance; returns a JSON report with score, grade, findings, and signed receipt.

Instructions

SiteScan API check: Machine-readable technical checks of one public page: security headers, SEO basics, accessibility signals, performance indicators. PAID: $0.50 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON report with score, grade, findings - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"url":"https://example.com"}.

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 observedv1.0.2

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare the safety profile (readOnly=false, openWorld=true, idempotent=false); the description adds materially important context they do not cover: a $0.50 USDC charge per call settled on Base via x402, drawn from a named wallet env var, described as real money. It also previews the return payload (score, grade, findings, signed receipt, settlement transaction), which is valuable given there is no output schema. It stops short of covering failure/refund behavior or rate limits.

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 definition is front-loaded with the purpose, then the payment terms, then the return shape and an example — a sensible information order. It is dense but each clause carries information; a light trim of the parenthetical payment mechanics would make it tighter.

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 one-parameter, no-output-schema tool, the description covers what an agent needs: what is scanned, what it costs, where the payment comes from, and what comes back. The notable gap is tier differentiation from the sibling sitescan_basic/business tools, which matters for correct tool selection.

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% and the single `url` parameter is already documented as a "public http(s) URL to audit". The description reinforces the public-page constraint and supplies an example input, but adds no new syntax, validation, or format rules beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

"Machine-readable technical checks of one public page" states a specific verb and resource, and the enumerated dimensions (security headers, SEO basics, accessibility, performance) make the output scope concrete. It does not, however, distinguish itself from plausible siblings like x420_sitescan_basic or x420_sitescan_business, so an agent cannot tell which scan tier to pick from this text alone.

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 "one public page" and the example input, which signals a single-URL audit rather than a crawl. There is no explicit when-to-use/when-not-to-use guidance and no routing to the basic or business variants, leaving tier selection to inference.

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