Skip to main content
Glama
Sign In

A11y Audit (ADA Lawsuit-Risk Scan)

by io.github.theharrisontruong-web
OverviewDiscussionsAdmin

audit_a11y_lite

Read-onlyIdempotent

FREE lite accessibility lawsuit-risk scan of a website URL. Runs the same 20 checks as audit_a11y but returns top-line results only: 0-100 score, A-F grade, lawsuit-risk level, check counts, and the titles of the top gaps — no per-check evidence, no detailed recommendations. Use this to triage whether a site needs the full audit_a11y report, or call audit_a11y directly for the complete evidence-backed scan. Automated scan — not a compliance certification.

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

Input Schema

NameRequiredDescriptionDefault
urlYesWebsite URL to scan, e.g. https://example-store.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds substantive behavior beyond that: the exact return payload (score, grade, risk level, check counts, top gap titles), what is deliberately omitted (no per-check evidence, no recommendations), and a scope disclaimer ('Automated scan — not a compliance certification'). With no output schema, this disclosure is the only source of return-shape information.

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?

Three sentences, each doing distinct work: identity and cost, output scope plus omissions, then routing guidance and disclaimer. Front-loaded with the key differentiator ('FREE lite... top-line results only') and free of repetition.

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?

For a single-param read-only scan with no output schema, the description supplies everything an agent needs: input intent, full return contents, what is excluded, and the tradeoff against the fuller sibling. Nothing material is missing.

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

Parameters4/5

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

Only one parameter with 100% schema coverage, so the schema already defines 'url' with an example. The description adds no syntax or format detail beyond it, but the baseline for fully documented params is 3-4 and the surrounding framing ('website URL to scan') is consistent with the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('lite accessibility lawsuit-risk scan of a website URL') and immediately distinguishes itself from sibling audit_a11y by scope ('returns top-line results only'). An agent can tell exactly what this tool produces without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit decision rule: use this to 'triage whether a site needs the full audit_a11y report,' or 'call audit_a11y directly for the complete evidence-backed scan.' The alternative and the condition selecting it are both named, leaving nothing to inference.

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

All A11y Audit (ADA Lawsuit-Risk Scan) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources