Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

color_blindness_check

Simulate protanopia, deuteranopia, tritanopia, and achromatopsia on a design node to uncover color accessibility issues.

Instructions

Simulate color blindness on a design to check for issues.

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": {
      "nodeId": "<nodeId>"
    },
    "name": "color_blindness_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoColor blindness type
nodeIdYesNode to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.3

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states intent, not effect. It does not say whether this is a read-only preview, whether it modifies the design, what the output looks like, or what side effects may occur.

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?

A single, front-loaded, waste-free sentence. It states the action, the object, and the goal without filler or repetition.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description leaves critical context missing: what the agent will receive after invocation, whether the operation is safe/destructive, and how 'issues' are reported. An agent can glean the tool's intent but not the full contract.

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%, so the schema already documents both parameters and the type enum. The description adds no additional meaning about how nodeId is resolved or how the type affects simulation, which keeps this at the baseline.

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?

The description uses a specific verb ('simulate') and names the resource ('a design') and outcome ('check for issues'), clearly distinguishing it from contrast-checking or accessibility-audit tools. It is slightly vague about what 'issues' means, but the core purpose is unambiguous.

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

Usage Guidelines2/5

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

The description implies it is used to preview color vision deficiencies, but gives no explicit guidance on when to choose this over sibling tools like check_contrast, audit_accessibility, or color_check_all. No alternatives or exclusions are mentioned.

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

Deploy Server

Other Tools