Skip to main content
Glama
ksmuvva

Accessibility MCP

by ksmuvva
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

audit_site

Crawl a website and audit each page for WCAG 2.2 accessibility violations using Axe, Pa11y, Lighthouse, or IBM engines. Returns per-page results and a GDS compliance summary.

Instructions

Crawl a site (same origin) and audit each page for WCAG 2.2 accessibility.

Breadth-first crawl from the start URL, auditing each page with the chosen engines. Returns per-page results and an aggregated service-level GDS summary.

Args: url: The start URL to crawl from. max_pages: Maximum pages to audit (capped by server config). max_depth: Maximum link depth from the start URL (capped by server config). level: WCAG level: "A", "AA" (default) or "AAA". engines: Subset of ["axe","pa11y","lighthouse","ibm"]. Defaults to ["axe"]. include_best_practice: Also run axe "best-practice" rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
levelNoAA
enginesNo
max_depthNo
max_pagesNo
include_best_practiceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

No annotations, but description details crawl algorithm, output, and parameter limits. Could note time/resource usage but still strong.

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?

Efficient: one sentence for purpose, one for method/output, then bullet-free Args list. No fluff.

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?

Covers purpose, algorithm, output summary, all parameters. Output schema exists so return details are sufficient.

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 has 0% coverage, but description fully explains all 6 parameters, including defaults, constraints, and valid values.

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?

Description explicitly states it crawls and audits a site for WCAG 2.2, distinguishing it from single-page or specific-engine tools like audit_url or audit_axe.

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

Usage Guidelines4/5

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

Clearly implies use for site-wide audits, with constraints like same-origin and server caps, but does not explicitly exclude single-page tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ksmuvva/MCp-accessibility-Muvva'

If you have feedback or need assistance with the MCP directory API, please join our Discord server