Skip to main content
Glama

build_color_palette

Create or expand color presets for selected fixtures by setting RGBW values, labels, and pool swatches in a single operation.

Instructions

Build (or extend) a color preset palette for a fixture selection in one call.

For each color: selects ``target``, sets R/G/B/W, stores the preset (Global by
default), labels it, and sets its pool appearance swatch.

To extend an existing palette to a new fixture group without disturbing
already-stored values, pass that group as ``target`` and ``merge=True``.

Args:
    target: A grandMA2 selection command (e.g. "Group 3", "Group 1 Thru 5").
    colors: List of {id, name?, r, g, b, w?} with r/g/b/w in 0-100.
    scope: "global" (default), "selective", or "universal".
    merge: Merge into existing presets (non-destructive extend).
    label: Apply each color's name as the preset label.
    appearance: Set each preset's pool swatch from its color.

Returns:
    str: Operation result message

Examples:
    - Build a palette on LED Par: target="Group 3", colors=[{"id":7,"name":"Red","r":100,"g":0,"b":0}]
    - Extend it to Wash: target="Group 4", merge=True, same colors

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYes
colorsYes
scopeNoglobal
mergeNo
labelNo
appearanceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the steps: select target, set colors, store, label, set appearance. However, it does not clarify whether non-merge calls overwrite existing presets or cause other side effects, nor does it mention permissions or error conditions.

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 well-structured with headings (Args, Returns, Examples) and front-loaded with purpose. It is not overly verbose, though some sentences could be tighter. Every major element earns its place.

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?

Given the tool's complexity (6 params, no annotations, output schema exists), the description covers purpose, parameters, return type, and examples. It lacks error handling and edge cases, but overall provides sufficient context for correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description must add value. The Args section explains each parameter beyond schema: e.g., target is a selection command, colors have r/g/b/w in 0-100, merge is non-destructive, scope defaults to global. This adds substantial meaning, though not exhaustive.

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 clearly states the tool builds or extends a color preset palette for fixture selections. It provides a specific verb ('Build (or extend)') and resource ('color preset palette') and differentiates from siblings like store_preset or build_preset_palette by detailing the multi-color, single-call behavior.

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 explicitly guides when to use merge for extending palettes without overwriting, and the examples show both fresh build and extension. However, it does not explicitly mention when not to use this tool or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chienchuanw/gma2-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server