Skip to main content
Glama

Status color check

color_meaning_check
Read-only

Check status or state colors for color-vision problems. Pass states as lines or comma-separated entries such as error: #d32f2f, success: #2e7d32, or an array of {label, color}. Labels like error, success, warning and info (and close variants) get matching icon and text suggestions; any other label gets generic ones. Every pair is compared by CIE76 deltaE under normal vision and simulated protanopia, deuteranopia and tritanopia (Machado et al. 2009, full severity). Under 10 counts as merged and under 20 as weak, both working conventions. Returns each pair's numbers, the worst case, a lightness gap, and a second cue per state with a reminder of WCAG 1.4.1 (Use of Color) and 1.4.11 (non-text contrast for the icon). Simulation covers dichromacy only; milder anomalous trichromacy falls between.

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": {
      "states": "<states>"
    },
    "name": "color_meaning_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
statesYesState colors with labels: "error: #d32f2f, success: #2e7d32" or an array of {label, color}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / states / description
      Previous value: -"State colours with labels: \"error: #d32f2f, success: #2e7d32\" or an array of {label, color}."New value: +"State colors with labels: \"error: #d32f2f, success: #2e7d32\" or an array of {label, color}."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint, the description discloses the comparison method (CIE76 deltaE under normal vision plus Machado 2009 protan/deutan/tritan simulation at full severity), the interpretation thresholds (<10 merged, <20 weak), what is returned, and an explicit limitation (dichromacy only; milder anomalies fall between). That is rich, trustworthy behavioural context.

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?

Purpose is front-loaded, then input formats, output, method, thresholds and caveat — a logical flow with no filler sentences. It is dense but every clause carries information; only the methodology citation could be trimmed.

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

Completeness5/5

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

With one parameter, no output schema and only safety annotations, the description supplies the missing pieces: output contents, thresholds for interpreting results, WCAG success-criteria reminders, and the simulation's coverage limits. Nothing needed to call or interpret it is absent.

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 the single parameter is already documented, but the description adds real semantics: accepted string and array forms, how labels map to matched vs generic icon/text suggestions, and which label names count as known variants.

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?

It states a specific verb and resource ('Check status or state colors') and scopes it to 'color-vision problems', which cleanly separates it from siblings like check_contrast, colour_palette_brief_check and chart_colour_check. An agent can tell what it does without reading 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 Guidelines4/5

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

The context is clear — status/state colours that must remain distinguishable under colour-vision deficiency — and it explains behaviour for recognised vs unknown labels. However, it never explicitly names alternatives (e.g. use check_contrast for plain WCAG ratios) or states when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources