Skip to main content
Glama

A11y Probe

scan_site

Read-only

Up to 10 same-origin pages, starting from start_url. authorized is true. Price 0.50 USD in USDC on Base, settled after a successful scan. Automated checks find roughly 57% of WCAG issues.

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": {
      "start_url": "<start_url>",
      "authorized": "<authorized>"
    },
    "name": "scan_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
standardNo
max_pagesNo
start_urlYes
authorizedYesTrue when the caller may scan this URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The pricing sentence (0.50 USD in USDC on Base, settled after a successful scan) is genuinely valuable context beyond readOnlyHint, telling the agent the call costs money and is billed only on success. The 57% coverage caveat usefully sets accuracy expectations. However, "authorized is true" merely restates a required const parameter, and nothing is said about rate limits, failure modes, or runtime.

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?

Four short sentences with the scope and cost front-loaded and no filler. The telegraphic fragments ("authorized is true.") read as clipped notes rather than polished prose, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and only 25% schema description coverage, the description should carry more weight. It never indicates what a scan returns (issue list, report reference, per-page results) or how the 'standard' option affects output, leaving the agent unable to predict the response shape.

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

Parameters2/5

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

Schema coverage is only 25%, so the description needs to compensate and largely does not. It clarifies the page cap and same-origin restriction, but leaves the four-value 'standard' enum (wcag2a through wcag22aa) and its default unexplained, and does not say whether max_pages defaults to 10.

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?

"Up to 10 same-origin pages, starting from start_url" gives a concrete verb-and-scope picture, and the WCAG reference identifies it as an accessibility audit rather than an arbitrary crawl. It never names scan_page as the single-page counterpart, so the agent must infer the distinction from the page limit alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use statement and no named alternative, even though scan_page exists in the sibling set. The 10-page cap only implicitly signals that this is the multi-page variant.

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.