Skip to main content
Glama

browser_axe_audit

Read-onlyIdempotent

Run an installed axe-core WCAG audit on the current locally approved browser page to detect accessibility violations without modifying the page.

Instructions

Run installed axe-core WCAG audit on the current locally approved browser page (read-only).

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": "browser_axe_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the '(read-only)' parenthetical in the description largely restates structured data. It adds modest value by naming the engine ('installed axe-core') and anchoring the run to the current page, but says nothing beyond annotations about failure modes, what happens if no page is open, or what the audit produces.

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?

A single front-loaded sentence with no filler. Slight deduction because 'locally approved' is undefined jargon that adds ambiguity rather than precision.

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?

No output schema exists, and the description never indicates what an axe-core audit returns (violation list, pass/fail counts, severity) or the failure condition when no approved page is present. For a zero-parameter tool this is close to sufficient, but the missing return shape leaves a real gap.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4; there is nothing the description could add. It correctly implies no configuration is accepted and the target is implicit (the current page).

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 specific verb and resource: runs an axe-core WCAG audit against the current browser page. The scope ('current locally approved browser page') is clear enough to distinguish it from a generic design_audit, though it never names the closest sibling (browser_accessibility_basic) so the agent must infer the split from tool names alone.

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

Usage Guidelines3/5

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

The phrase 'current ... browser page' implies a precondition (a page must already be opened/approved) but never states it as a requirement or as an exclusion. There is no explicit when-to-use-this-vs-browser_accessibility_basic guidance, so selection between the two accessibility tools is left to inference.

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