Skip to main content
Glama

simulate_color_blindness

Read-onlyIdempotent

Simulate how colors appear to viewers with protanopia, deuteranopia, tritanopia, their milder anomaly forms, or achromatopsia, so you can check palettes for accessibility.

Instructions

Simulate how one or more colors appear to viewers with color vision deficiency (protanopia, deuteranopia, tritanopia, their milder anomaly forms, or achromatopsia).

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_color_blindness"
  }
}

Input Schema

NameRequiredDescriptionDefault
typesNoDeficiency types to simulate. Defaults to all 7 (dichromacy + anomaly + achromatopsia).
colorsYesColors to simulate (hex, rgb, hsl), up to 64

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the scope of simulated deficiency types but does not describe the return format, result ordering, or how multiple colors and deficiency types are presented.

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?

The description is a single well-formed sentence with no redundant wording. The purpose and supported deficiency types are front-loaded and easy to scan.

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 simulation tool with full schema coverage and rich annotations, the description provides enough context to invoke it correctly. The remaining gap is that it does not describe the output shape, which matters somewhat because no output schema is present.

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%, so the schema already documents both parameters, including color formats, the 64-color limit, and the default of all seven deficiency types. The description reinforces the color/deficiency scope but adds no syntax or behavioral detail beyond the 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?

The description gives a specific verb and resource: simulate how colors appear under named color-vision deficiencies. It accurately lists the supported conditions (protanopia, deuteranopia, tritanopia, anomaly forms, achromatopsia), so an agent can distinguish it from adjacent accessibility tools like check_contrast or check_palette_accessibility.

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 description implies when to use the tool by stating that it simulates how colors appear to viewers with color-vision deficiency. However, it does not explicitly contrast this with alternatives such as contrast checking or accessibility auditing, nor does it state exclusions or prerequisites.

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