Skip to main content
Glama
snayyar00

@webability/mcp

by snayyar00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Start a full accessibility audit

start_audit

Start a full accessibility audit for a URL to generate a timestamped, downloadable report and Excel workbook for compliance evidence. Returns an audit ID for polling progress.

Instructions

[Full — FREE with a WebAbility account. Not runnable in Lite. Connect hosted MCP at https://mcp.webability.io/mcp (dashboard or Smithery: webability/accessibility), authenticate, then call start_audit.] Kick off a FULL accessibility audit deliverable for a URL — a persistent, timestamped artifact, not an inline scan. Runs the server-side pipeline (axe + advanced checks + mobile viewports + annotated screenshots + optional agent spot-check) and produces a downloadable report and a formatted Excel workbook (Cover / Status / Barriers / ADA context sheets) stored durably. Returns immediately with an audit id; poll get_audit for progress and, when complete, download URLs. Use this when someone needs a durable artifact to attach as evidence of testing effort for a compliance officer or legal response — for iterating on code, use scan_page + verify_fix instead. Free for everyone; needs a free WebAbility account (sign in by connecting https://mcp.webability.io/mcp/auth, or run webability login). Set includeAgent:true to add the slower agentic manual-audit pass. To audit a local dev server, open a tunnel (webability-tunnel --port 3000) and pass its URL as url with the printed secret as tunnel_secret; keep the tunnel open until get_audit reports complete (about 5 minutes) — the pipeline loads the page several times.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to audit (a public/staging URL the server can reach, or a webability-tunnel URL — not localhost)
includeAgentNoAlso run the agentic manual-audit pass (keyboard/focus/modal exploration). Slower. Default false.
tunnel_secretNoSecret printed by `webability-tunnel`. Required when `url` is a tunnel URL; the URL alone will be refused by the relay. Ignored otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.0
    • changedInput schema / properties / includeAgent / description
      Previous value: -"Also run the agentic manual-audit pass (keyboard/focus/modal exploration). Slower and paid. Default false."New value: +"Also run the agentic manual-audit pass (keyboard/focus/modal exploration). Slower. Default false."
    • addedInput schema / properties / tunnel_secret
      Added value: +{
+  "description": "Secret printed by `webability-tunnel`. Required when `url` is a tunnel URL; the URL alone will be refused by the relay. Ignored otherwise.",
+  "type": "string"
+}
    • changedInput schema / properties / url / description
      Previous value: -"URL to audit (a public/staging URL the server can reach — not localhost)"New value: +"URL to audit (a public/staging URL the server can reach, or a webability-tunnel URL — not localhost)"
  2. First observedv1.3.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnly=false, idempotent=false, openWorld=true; the description adds substantially more: async fire-and-return with an audit id, polling via get_audit, durable server-side storage, downloadable report plus Excel workbook, ~5 minute runtime, the page being loaded several times, and the requirement to keep the tunnel open until completion.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is dense and mostly earns its place, but the bracketed setup paragraph plus a second 'Free for everyone' statement duplicate the free/account requirement, and the tunnel workflow detail is long. Front-loading of the deliverable framing is good, but there is redundancy.

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?

With no output schema, the description fully carries the return-value burden: it explains the immediate id return, the get_audit polling loop, and the eventual download URLs. For a multi-step async tool with auth and tunnel prerequisites, nothing an agent needs to invoke and follow up is missing.

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 description coverage is 100%, so all three parameters are already documented. The description restates includeAgent and tunnel_secret behavior largely in line with the schema, adding only the workflow note that the tunnel must stay open; baseline 3 applies when the schema carries the load.

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+resource (start a FULL accessibility audit deliverable for a URL) and immediately scopes it as a persistent, timestamped artifact rather than an inline scan. It explicitly names the sibling it is not (scan_page + verify_fix for iterating on code), so an agent can differentiate without opening schemas.

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 explicit when-to-use ('durable artifact to attach as evidence for a compliance officer or legal response') and when-not-to-use with the named alternative (scan_page + verify_fix). It also states prerequisites: free account, hosted MCP connection, and the tunnel workflow for local dev servers.

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

Deploy Server

Other Tools