Skip to main content
Glama
snayyar00

@webability/mcp

by snayyar00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Verify an accessibility fix

verify_fix
Read-onlyIdempotent

Re-scan a fixed page element after your accessibility fix to confirm the violation is gone, returning verified true or false for the URL and selector.

Instructions

Re-scan a specific element after applying an accessibility fix and confirm the violation is gone — closes the loop that find-only tools leave open. After you edit the code and serve it (deployed, staging, or http://localhost:3000), call this with the URL and the selector you fixed to get a machine-checked verified: true|false (DOM engines only — visual_audit findings are out of scope). Pass the WCAG criterion (e.g. "1.1.1") or axe rule id (e.g. "color-contrast") to check just that criterion; omit it to require the element be clean of ALL violations. A blocked page (bot-challenge / HTTP error) is reported as unverified, never a pass — verification fails closed. If the selector matches no element, the result is verified: false with reason "not-found" — pass the element's current selector, or re-run scan_page if your fix removed the element. Pair with scan_page → generate_ai_fix → verify_fix for a full find-fix-verify cycle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL now serving the fix (deployed, staging, or http://localhost:3000). Also accepted as `page` or `pageUrl`.
wcagNoOptional: WCAG criterion (e.g. "1.1.1", "1.4.3") or axe rule id (e.g. "color-contrast") to verify specifically. Omit to require the element be free of ALL violations.
selectorYesCSS selector of the element you fixed — use the `selector` from the original scan_page issue
viewportNoViewport size (default: desktop). Use the same viewport the issue was found at.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.0
    • changedInput schema / properties / url / description
      Previous value: -"URL now serving the fix (deployed, staging, or http://localhost:3000)"New value: +"URL now serving the fix (deployed, staging, or http://localhost:3000). Also accepted as `page` or `pageUrl`."
  2. First observedv1.3.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, but the description adds substantial behavior beyond them: verification fails closed, a blocked page (bot-challenge/HTTP error) yields unverified rather than a pass, and a no-match selector returns verified: false with reason "not-found". These are exactly the failure-mode details an agent needs to interpret results correctly.

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?

Front-loaded with the core action and the loop it closes, and every sentence carries operational content. It is denser and longer than strictly necessary — several em-dash clauses and edge cases could be tightened — but nothing is filler.

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 read-only verification tool with no output schema, the description still conveys the return shape (verified boolean plus a reason value), the engine limitation (DOM engines only), and the recovery path for a missing selector. Nothing an agent needs to call it or interpret it is missing.

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

Parameters5/5

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

Schema coverage is 100%, but the description still adds meaning: the WCAG/axe parameter narrows verification to one criterion while omitting it requires the element to be clean of ALL violations, and the selector should be the one carried over from the original scan_page issue. It also advises reusing the same viewport the issue was found at, which the schema does not state.

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 precise verb+resource: re-scan a specific element after a fix and confirm the violation is gone, producing a machine-checked verified: true|false. It explicitly scopes itself against siblings ("closes the loop that find-only tools leave open") and excludes visual_audit findings, so an agent can distinguish it from scan_page, visual_audit, and diff_scan without opening a 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 explicit preconditions (edit the code and serve it — deployed, staging, or localhost), the exact moment to call it, and the workflow it belongs to (scan_page → generate_ai_fix → verify_fix). It also names what is out of scope (visual_audit findings) and what to do when the selector matches nothing (pass the current selector or re-run scan_page), which is unusually complete routing guidance.

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