Skip to main content
Glama

Simulate Color Blindness

simulate_colorblind

Simulate protanopia, deuteranopia, tritanopia, and achromatopsia on a list of colors, then flag pairs that become hard to distinguish to catch inaccessible color choices.

Instructions

Simulate protanopia, deuteranopia, tritanopia and achromatopsia for a list of colors and flag pairs that look different normally but become hard to tell apart (like red vs green status badges). Deterministic, no API key needed.

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

Input Schema

NameRequiredDescriptionDefault
colorsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does useful work: it discloses the output behavior (flagging pairs that collide under simulation) and operational traits (deterministic, no API key needed). It does not state whether results include per-color simulated values or only pair flags, leaving some output shape to inference.

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, front-loaded with the capability and immediately followed by the concrete output value and an illustrative example. Every clause earns its place; nothing is padding.

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 single-parameter, side-effect-free computation tool with no output schema, the description supplies enough to call it correctly and anticipate the return value. The remaining gap is input format detail (hex string conventions) rather than missing conceptual context.

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 0% for the single 'colors' array, so the description must compensate, and it only partly does: it says 'a list of colors' but never specifies hex format (with or without '#'), whether alpha is supported, or what the optional 'name' field is used for in flagged output. The nested hex/name structure is left to the 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?

Names a specific verb (simulate) and the exact resource (four named color-vision deficiencies) applied to a list of colors, plus the distinctive confusable-pair output. It is clearly separable from contrast-oriented siblings like check_contrast or contrast_matrix, though it never explicitly contrasts itself with them.

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 parenthetical example ('red vs green status badges') implies the intended use case: validating that colors stay distinguishable for colorblind users. However, there is no explicit when-not guidance and no pointer to alternatives such as check_contrast or audit_accessibility for broader accessibility checks.

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