Skip to main content
Glama

check_palette_accessibility

Read-onlyIdempotent

Audit color palettes for color-blind accessibility by reporting Delta E 2000 distances under CVD types and flagging color pairs that become indistinguishable.

Instructions

Audit a color palette for color-blind accessibility. For each pair of colors, reports the perceptual distance (Delta E 2000) under each CVD type and flags pairs that become indistinguishable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "colors": "<colors>"
    },
    "name": "check_palette_accessibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
typesNoCVD types to audit. Defaults to all 7.
colorsYesPalette colors to audit (2-64)
indistinguishableThresholdNoΔE2000 below which two simulated colors are considered indistinguishable (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/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 safety is covered. The description contributes genuine behavioral context by naming the metric (Delta E 2000), the granularity (per color pair, per CVD type), and the flagging outcome. It stops short of describing the response structure for flagged versus passing pairs, which matters since there is no output schema.

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, zero filler, with the purpose and scope front-loaded and the output semantics immediately following. Every clause carries information an agent needs.

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?

For a three-parameter, read-only analysis tool with full schema coverage and no output schema, the description covers what is computed and what is flagged. It is slightly thin on output shape (per-pair reporting format, whether results are grouped by CVD type) and on scale/pagination for the 64-color maximum, which would produce over 2,000 pairs.

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?

Schema coverage is 100%, so all three parameters (colors, types, indistinguishableThreshold) are documented with ranges and defaults. The description corroborates and frames them ('for each pair of colors', 'become indistinguishable'), linking the threshold parameter to the core concept, but adds little syntax or meaning the schema does not already carry.

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?

States a specific verb and resource ('Audit a color palette') plus the exact scope ('color-blind accessibility'), and goes further to say what the audit computes: per-pair Delta E 2000 across CVD types with indistinguishable pairs flagged. An agent can separate this from contrast checking or plain color-blindness simulation without opening the schema.

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 use case is implied clearly by the purpose statement, so an agent knows this is the tool for CVD accessibility validation. However, there is no explicit when-to-use framing versus siblings like simulate_color_blindness (which shows a simulation) or check_contrast (which measures contrast ratios), and no stated prerequisites or exclusions.

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