Skip to main content
Glama

audit_ui_colors

Read-onlyIdempotent

Audit all UI foreground/background pairs and optional swatches in one call for WCAG, APCA, color-blindness, simultaneous-contrast, and disliked-color issues, with hue-preserving fixes.

Instructions

Audit an entire UI's foreground/background pairs and optional palette swatches in one call. Checks WCAG 2.x, APCA Lc, color-blindness contrast collapses, simultaneous-contrast vibration, and universally disliked colors — and provides exact hue-preserving fixes for every failing pair.

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

Input Schema

NameRequiredDescriptionDefault
pairsNoForeground/background pairs to audit (up to 100)
swatchesNoOptional standalone palette swatches to check for bile-zone/CVD collisions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the specific audit lenses (WCAG 2.x, APCA Lc, CVD collapses, simultaneous contrast, disliked colors) and that it returns hue-preserving fixes. It does not disclose the shape of the report, whether all failures are listed or capped, or runtime characteristics, so it stays at a solid 3 rather than higher.

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?

Two sentences, both front-loaded with the operation and then the checks/output. Every clause adds information — the check list and the fix guarantee are not padding — and nothing repeats the name or the annotations.

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, read-only, idempotent audit with fully documented schema and no output schema, the description covers what is checked and what comes back (per-pair fixes). The remaining gap is the structure of the returned report — pass/fail per check versus a combined verdict — which an agent would still have to discover by calling 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 description coverage is 100% and the nested pair object documents bg, fg, name and role with per-role contrast thresholds, so the schema already carries full parameter meaning. The description only restates the two inputs at a high level ('pairs and optional palette swatches') and adds no format or syntax detail, which matches the baseline 3 for a fully-documented schema.

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 states a specific verb and resource ('Audit an entire UI's foreground/background pairs and optional palette swatches') and enumerates the five check families it runs plus its fix output. The phrase 'entire UI ... in one call' implicitly separates it from single-pair siblings like check_contrast, but no sibling is named explicitly, so an agent must infer the routing.

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?

Usage is only implied by 'entire UI ... in one call' and 'optional palette swatches' — the reader can deduce this is the batch audit versus single-pair tools. There is no explicit when-to-use/when-not statement, no prerequisite note, and no guidance on choosing between this and check_palette_accessibility or analyze_palette_consistency.

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