Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

color_darkmode

Convert any Figma frame into a dark mode variant by intelligently mapping colors, while preserving your specified brand color.

Instructions

Generate a dark mode variant of a frame, mapping all colors intelligently.

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

Input Schema

NameRequiredDescriptionDefault
nodeIdYesFrame to convert
brandColorNoBrand color to preserve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.3

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the tool creates a new node or mutates the existing frame, whether the original is preserved, or what 'intelligently' means in terms of color transformations.

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?

The description is a single, front-loaded sentence with no wasted words. The word 'intelligently' is vague and adds little, but overall the structure is appropriately concise.

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?

With no output schema and no annotations, the description should clarify whether the tool returns a new node, modifies in place, or how brandColor is preserved. None of this is addressed, making it incomplete for an agent deciding how to invoke and interpret the result.

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 nodeId and brandColor. The description adds no parameter-specific meaning beyond the generic notion of a frame and colors.

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 uses a specific verb ('Generate') with a clear resource ('a dark mode variant of a frame') and states the action ('mapping all colors intelligently'). It also distinguishes itself from the sibling color_lightmode tool without ambiguity.

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 description clearly implies when to use this tool: when a dark mode variant of a frame is needed. However, it does not explicitly mention when not to use it or name the alternative color_lightmode, leaving some routing to inference.

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