Skip to main content
Glama

x420_sitescan_business

Run a multi-page website audit with sitemap checks and recommendations. Returns a JSON report with a signed receipt and settlement transaction for each paid call.

Instructions

SiteScan Business: Expanded multi-page audit with sitemap check and recommendations. PAID: $7.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=7 (or higher) is set in the MCP server's environment. Returns: JSON report, up to 4 pages - 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_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYespublic http(s) URL to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.9/5.0
Behavior5/5

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

Annotations cover safety (readOnlyHint false, destructiveHint false, openWorldHint true), but the description adds the material behavior an agent cannot see elsewhere: a real $7.00 USDC charge on Base via x402, the wallet env var used, and the fact that the call is refused until X420_MCP_MAX_USD is raised to 7 or more. It also states the return shape (JSON report plus signed receipt and settlement transaction) and the 4-page ceiling.

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?

Purpose is front-loaded in the first clause, followed by pricing, environment prerequisite, return value, and an example — a sensible information order. It is dense for a single paragraph but nearly every clause carries operational weight; the example input is marginal given a one-parameter schema.

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, open-world, one-parameter audit tool with no output schema, the description covers cost, payment rail, the configuration prerequisite, the page limit, and what comes back. It omits what happens on failure or whether a declined or errored audit is still charged, which matters for a tool that spends real money.

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% with a single required string parameter already documented as "public http(s) URL to audit." The description only repeats this via an example input, adding no constraints on URL validation or redirect handling 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 opens with a specific verb-and-resource framing ("Expanded multi-page audit with sitemap check and recommendations") and signals scope with "up to 4 pages." The word "Expanded" implicitly distinguishes it from a lighter variant, but no sibling is named, so the differentiation is left to inference.

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 context is implied rather than stated: the $7.00 tier and multi-page scope suggest this is for deeper audits than a cheap single-page check, but there is no explicit "use this instead of X when Y." The only hard gating information is the budget-cap requirement, which is operational rather than about choosing between tools.

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