Skip to main content
Glama
Colors MCP Server

Colors MCP Server

by HtetOoWaiYan

Color blindness simulation

colors_vision
Read-onlyIdempotent

Simulate color blindness to see how colors appear and measure whether sets stay distinguishable, flagging the weakest pair per vision type so you can check chart and status colors before red/green pairs collide.

Instructions

Simulate how colors look with color blindness (Machado 2009 model) and, for 2+ colors, measure whether the set stays distinguishable: returns the weakest pair per vision type. Use to check chart or status colors, or to find out if red/green pairs will collide. To BUILD a color-blind-safe set use colors_palette with kind "categorical".

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

Input Schema

NameRequiredDescriptionDefault
typeNoWhich color vision to simulate. "deuteranopia" and "protanopia" are red-green; "tritanopia" is blue-yellow; "achromatopsia" is no color; "all" (default) runs all four.all
colorsYesColors to simulate (and compare with each other). A list, even for a single color. Any CSS color strings.
minDifferenceNoA pair counts as distinguishable when its CIEDE2000 difference is at least this. Default 10.

Output Schema

NameRequiredDescriptionDefault
separationYes
simulationsYes
allDistinguishableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add semantics beyond that, which it does: it names the Machado 2009 model, discloses that comparison only kicks in for 2+ colors, and states the return shape ('weakest pair per vision type'). It stops short of explaining how the weakest pair is chosen or what the single-color case returns, but that is largely covered by the 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: capability and return shape first, then usage and the sibling hand-off. Every clause carries information an agent would otherwise have to infer.

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 rich annotations, a complete input schema, and an output schema, the description supplies exactly the missing layer: what the tool computes, when to reach for it, and where to go instead. Nothing needed to select or invoke it correctly is absent.

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 the schema already documents the vision-type enum, the color list including mutual comparison, and the minDifference CIEDE2000 threshold with its default. The description adds only the implicit condition that distinguishability measurement requires 2+ colors, which is a modest increment over a fully documented schema.

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 ('Simulate how colors look with color blindness') and adds the second capability ('measure whether the set stays distinguishable'), plus names the sibling it is not. An agent can distinguish it from colors_palette and colors_audit without opening any schema.

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

Usage Guidelines5/5

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

Gives concrete use cases (check chart or status colors, predict red/green collisions) and an explicit alternative with the exact parameter to use instead ('colors_palette with kind "categorical"') when the goal is building rather than testing. When-to-use, when-not-to-use, and the routing target are all present.

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