Skip to main content
Glama

WritersLogic business agents

accessibility-patcher

ADA / WCAG Lawsuit Shield & DOM Auto-Patcher — Returns a FAIL / REVIEW / PASS verdict for a page's HTML (pasted or fetched from a URL) against the WCAG failures most cited in ADA demand letters: alt text, form labels, unnamed buttons and links, lang, headings, landmarks, skip links, zoom. Each issue carries a CSS selector, source line and fix, with a top-five list, a SARIF 2.1.0 log, a litigation risk score, per-element patched HTML and an int

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "accessibility-patcher"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to audit. Provide url or html.
htmlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a lot of output behavior: a three-valued verdict, per-issue selectors and fix lines, a top-five list, SARIF 2.1.0 output, and a litigation risk score. It does not clarify the critical ambiguity of whether the 'Auto-Patcher' name means it modifies the target page or only returns patched HTML, nor does it cover fetching behavior, rate limits, errors, or what happens when neither input is supplied; the text also truncates mid-sentence ('and an int').

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?

Placeholder for internal check.

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 two-parameter, zero-required tool with no annotations and no output schema, the description does a fair job enumerating deliverable artifacts, so the agent knows what comes back. It falls short on the mutation/read boundary implied by 'Auto-Patcher', on the empty-input case, and on the truncated ending, leaving meaningful operational gaps.

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 50%: `url` is documented in the schema, `html` is not, so the description's 'pasted or fetched from a URL' phrase does add real meaning by indicating html is inline markup while url triggers a fetch. However, it does not state precedence when both are given, nor what the behavior is when both are omitted despite zero required parameters, and neither max length (2,048 / 2,000,000) is echoed.

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 concrete verb and resource: it audits a page's HTML against specific WCAG failure categories and returns a FAIL/REVIEW/PASS verdict, and it enumerates the check families (alt text, form labels, lang, headings, landmarks, skip links, zoom). The only blurring is the marketing headline 'ADA / WCAG Lawsuit Shield & DOM Auto-Patcher', which momentarily reads like a patching/mutation tool rather than an auditor.

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 when-to-use guidance, no prerequisites, and no alternatives named or excluded; the description never says when an agent should call this versus any other audit tool. The only usage-shaped guidance ('pasted or fetched from a URL') merely restates the two parameters.

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.

Resources