Skip to main content
Glama

A11y Probe

report

Read-only

A template Markdown accessibility report in de, fr, or en, with a prioritised fix list. Not legal advice and no compliance guarantee. No model calls. Price 1.00 USD in USDC on Base, settled after a successful scan.

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": "report"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNo
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

B3.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the burden and does deliver real context: no model calls, a flat 1.00 USD price in USDC on Base, and settlement only after a successful scan, plus explicit 'not legal advice / no compliance guarantee' disclaimers. It still omits delivery format specifics and what happens on scan failure or payment failure, and the money-charging side effect sits somewhat awkwardly beside readOnlyHint (though it is not a data-mutation claim).

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 clauses, front-loaded with the deliverable and then the disclaimers and pricing; almost every sentence carries information an agent would actually need. Slightly fragmented as sentence fragments rather than prose, but there is no padding.

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 five-parameter tool with no output schema and only readOnlyHint for annotations, the description covers the commercial and legal framing well but leaves key gaps: no explanation of what the report contains beyond a fix list, no scan scope/timing behaviour, and no semantics for standard or max_pages. Adequate to start a call, not complete enough to call confidently.

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 20% — just 'authorized' is documented — so the description needed to compensate and barely does. It mentions language options ('de, fr, or en') although the schema already carries that enum, but says nothing about start_url, standard (wcag2a/2aa/21aa/22aa), or max_pages (1–10), leaving four of five parameters semantically thin.

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 names a specific deliverable — a template Markdown accessibility report with a prioritised fix list, available in de/fr/en — which is concrete enough for an agent to know what the tool produces. It lacks an explicit action verb (generates? purchases?) and never contrasts itself with the scan_page/scan_site siblings, but the resource itself is unmistakable.

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 stated when-to-use or when-not-to-use guidance and no reference to the sibling tools, so an agent cannot tell from this text whether it should call report instead of scan_page or scan_site. The only implicit routing signal is the price/settlement note ('settled after a successful scan'), which hints at a paid workflow but does not define the selection condition.

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.