Skip to main content
Glama

validate_all_accessibility

Run comprehensive accessibility tests using Axe and WAVE to identify WCAG compliance issues on websites for improved user experience.

Instructions

Run all accessibility tests (Axe + optionally WAVE if API key provided).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
waveApiKeyNoOptional WAVE API key
wcagLevelNoWCAG level for Axe

Implementation Reference

  • Core handler function implementing 'validate_all_accessibility' tool. Runs Axe accessibility analysis always, and WAVE if API key provided. Aggregates results and counts total violations.
    export async function runAllAccessibility(
      url: string,
      options: AccessibilityTestOptions = {}
    ): Promise<AllAccessibilityResult> {
      const results: AllAccessibilityResult = {
        url,
        timestamp: new Date().toISOString(),
        summary: {
          tools_run: [],
          total_violations: 0,
        },
      };
    
      // Always run Axe (free, open source)
      results.axe = await analyzeAxe(url, options.axe || {});
      results.summary.tools_run.push('axe');
      results.summary.total_violations += results.axe.violations;
    
      // Optional: WAVE (requires API key)
      if (options.wave?.apiKey) {
        results.wave = await analyzeWAVE(url, options.wave);
        results.summary.tools_run.push('wave');
        results.summary.total_violations += results.wave.errors + results.wave.contrast_errors;
      }
    
      return results;
    }
  • index.ts:248-258 (registration)
    MCP tool registration including name, description, and input schema definition.
    name: 'validate_all_accessibility',
    description: 'Run all accessibility tests (Axe + optionally WAVE if API key provided).',
    inputSchema: {
      type: 'object',
      properties: {
        url: { type: 'string' },
        waveApiKey: { type: 'string', description: 'Optional WAVE API key' },
        wcagLevel: { type: 'string', description: 'WCAG level for Axe' },
      },
      required: ['url'],
    },
  • MCP server request handler switch case for the tool, validates arguments and delegates to runAllAccessibility.
    case 'validate_all_accessibility': {
      const validatedArgs = AllAccessibilityArgsSchema.parse(args);
      const result = await runAllAccessibility(validatedArgs.url, {
        wave: validatedArgs.waveApiKey ? { apiKey: validatedArgs.waveApiKey } : undefined,
        axe: { wcagLevel: validatedArgs.wcagLevel },
      });
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
  • Zod schema for input validation of the tool arguments.
    const AllAccessibilityArgsSchema = z.object({
      url: z.string().url(),
      waveApiKey: z.string().optional(),
      wcagLevel: z.string().optional(),
    });
  • TypeScript interface defining options for accessibility tests.
    export interface AccessibilityTestOptions {
      wave?: { apiKey: string };
      axe?: { wcagLevel?: string };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions running tests but doesn't disclose behavioral traits such as execution time, rate limits, error handling, or what happens if tests fail. For a tool with no annotations and potential external API calls, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that front-loads the core action and includes key details (Axe + WAVE, API key condition). There is no wasted text, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of running multiple accessibility tests, no annotations, and no output schema, the description is incomplete. It doesn't cover what the tool returns, how results are formatted, or any dependencies like network requirements, leaving the agent with insufficient context for effective use.

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 67% (2 out of 3 parameters have descriptions), so the baseline is 3. The description adds minimal value beyond the schema by implying that 'waveApiKey' enables WAVE testing, but it doesn't explain parameter interactions or provide additional context for 'wcagLevel' or 'url'.

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?

The description clearly states the action ('Run all accessibility tests') and specifies which tests (Axe + optionally WAVE), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'validate_accessibility_axe' or 'validate_accessibility_wave', which would require a 5.

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?

The description mentions that WAVE is optional if an API key is provided, giving some context, but it lacks explicit guidance on when to use this tool versus alternatives like the individual Axe or WAVE tools, or other comprehensive validation tools. No when-not-to-use scenarios or clear prerequisites are stated.

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/cordlesssteve/webby-mcp'

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