Skip to main content
Glama

A11y Probe

scan_page

Read-only

One public page checked for WCAG issues. authorized is true. No login, cookies, or stored page content. Price 0.05 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": {
      "url": "<url>",
      "authorized": "<authorized>"
    },
    "name": "scan_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http or https URL.
standardNo
authorizedYesTrue when the caller may scan this URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds substantial behavior the annotation cannot carry: per-scan price of 0.05 USD in USDC on Base, settlement occurring only after a successful scan, and an explicit warning that automated checks catch roughly 57% of WCAG issues. It stops short of covering rate limits, latency, or how results are delivered.

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?

Five short sentences with the core purpose front-loaded and no filler prose. The telegraphic 'authorized is true' sentence is largely redundant with the schema const, a minor wasted line.

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

Completeness3/5

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

For a paid, read-only scan with no output schema, pricing and settlement timing are well covered, but the description never says what a scan returns or whether the call blocks or hands off to the report sibling. An agent must still infer the result shape.

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 67 percent, so the schema documents url and authorized while the standard enum has no description. The description's 'authorized is true' merely restates the schema const, and it gives no meaning to the standard values (wcag2a, wcag22aa, etc.), so it does not compensate for the uncovered parameter.

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 single public page is checked for WCAG issues. The phrase 'One public page' implicitly scopes it against the sibling scan_site, and 'No login, cookies, or stored page content' further bounds the target, though no sibling is named explicitly.

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 exclusion of login-protected and stored content implies when not to use it, but there is no explicit guidance on choosing this over scan_site or get_pricing, and no stated prerequisites beyond the authorized flag.

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.