Skip to main content
Glama
Sign In
conductor-figma

conductor-figma

by Dragoon0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

suggest_color_palette

Generate a color palette from a single brand color, producing dark, light, or both mode variants. Use one hex input to derive consistent shades for Figma design systems.

Instructions

Generate a color palette from a single brand color.

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": {
      "brandColor": "<brandColor>"
    },
    "name": "suggest_color_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoMode (default: both)
brandColorYesBrand color hex

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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that a palette is generated; it does not disclose whether this mutates the document, returns a palette, creates styles, or how the 'mode' affects behavior. This is minimal and leaves key behavioral traits unspecified.

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 sentence with no wasted words, and the primary action and input are front-loaded. It is appropriately sized for a tool with only two simple parameters.

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?

There is no output schema and no annotations, yet the description does not explain return shape, side effects, or how mode is used. For an agent to invoke this tool confidently, more context is needed about what 'generate' produces and when this tool should be chosen over similar palette-related siblings.

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 'brandColor' as a hex value and 'mode' as dark/light/both. The description adds little beyond 'single brand color', so it does not exceed the baseline value the schema already provides.

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 states a clear verb ('Generate'), a resource ('color palette'), and an input constraint ('from a single brand color'). It is specific enough to convey the core operation, but it does not differentiate this tool from the very similarly named sibling 'color_palette_generate'.

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 gives no when-to-use guidance, no exclusions, and no mention of alternatives. With siblings like 'color_palette_generate' and 'export_color_palette', an agent has no basis for deciding when this tool is preferred.

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