Skip to main content
Glama

Audit accessibility

kaava_audit
Read-only

Audit design tokens against WCAG 2.2 AA in light and dark modes, checking contrast, visible boundaries, color-vision status distinctions, target sizes, and minimum text size.

Instructions

Accessibility audit of the current design system against WCAG 2.2 AA, in light and dark. Checks every promised foreground/background pairing (4.5:1 text, 3:1 UI, with APCA Lc for reference), whether solid fills have a visible boundary, whether status colors stay distinguishable with color-vision deficiencies (protanopia, deuteranopia, tritanopia), control target sizes and minimum text size. Run after overriding colors or sizes. It audits the tokens, not rendered pages.

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

Input Schema

NameRequiredDescriptionDefault
projectRootNoAbsolute path of the project. Defaults to the first workspace root the client exposes, else the server working directory.
failuresOnlyNoList only failures and warnings. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: the exact criteria evaluated (4.5:1 text, 3:1 UI, APCA Lc reference, boundary visibility, CVD simulation across three deficiency types, target and text sizes) and the token-vs-rendered-page limitation. It does not say whether warnings differ from failures in the report, but that is minor.

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 purpose, then the checklist, then the usage trigger and the key limitation. Every clause carries information, though the middle sentence is a long comma-chained list that could be tightened for scanability.

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

Completeness4/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, read-only audit tool with no output schema, the description supplies enough to call it correctly: what is checked, when to run it, and the token-only boundary. What the report looks like is left implicit, but an output schema does not exist to demand it.

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 100% and both parameters are fully documented in the schema, so the description is not required to compensate. It adds no meaning about projectRoot scoping or failuresOnly behavior, leaving the baseline 3 appropriate.

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?

Names a specific verb and resource ('Accessibility audit of the current design system against WCAG 2.2 AA') and immediately delimits scope: light and dark, token-level checks. The closing line 'It audits the tokens, not rendered pages' separates it from a rendered-page or single-pairing checker such as kaava_check_contrast.

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?

'Run after overriding colors or sizes' gives a clear triggering condition and sequencing hint. It stops short of naming an alternative for narrower checks (e.g. a single contrast pairing) or stating when not to run a full audit, so it falls short of a 5.

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