Skip to main content
Glama

x420_sitescan_basic

Audit a public website’s technical setup and robots.txt, returning a JSON report with signed receipt and settlement transaction.

Instructions

SiteScan Basic: Technical summary of a public website including robots.txt review. PAID: $3.00 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Above the default $1.00 per-call cap: refused until X420_MCP_MAX_USD=3 (or higher) is set in the MCP server's environment. Returns: JSON report - 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_basic"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYespublic http(s) URL to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare openWorldHint and non-readonly/non-idempotent, leaving cost, auth and side effects unexplained; the description fills exactly that gap. It discloses the $3.00 USDC price, the Base/x402 settlement path, the wallet key source, the failure mode when the per-call cap is too low, and what the response contains (deliverable plus signed receipt and settlement transaction).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, followed by payment terms, return shape, and an example — each sentence carries distinct operational information. There is no filler, and the payment/config detail is necessary because it gates invocation.

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 correctly spells out the return payload (JSON report, signed receipt, settlement transaction). Combined with price, environment prerequisite, and an input example, an agent has everything needed to invoke it correctly or recognize that it must reconfigure the cap first.

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 fully described as a public http(s) URL, so baseline is 3. The example input {"url":"https://example.com"} adds a small amount of concrete formatting value but no meaning the schema does not already carry.

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?

States a specific verb and resource: a 'Technical summary of a public website including robots.txt review', which tells an agent exactly what it gets back. It lacks any differentiation from the closely named siblings x420_sitescan_business and x420_sitescan_check, so an agent must guess which scan tier to pick.

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 a strong usage precondition — it is refused unless the $1.00 cap is raised via X420_MCP_MAX_USD — which is real when-to-use guidance. However, it never says when to choose this basic scan over the business/check variants, and there are no exclusions for non-public or non-HTTP URLs beyond the schema.

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