Skip to main content
Glama

build_preset_palette

Build a preset palette for color, beam, or focus by combining per-fixture-type attribute values into multiple targets within each preset.

Instructions

Build a preset palette of any type from per-fixture-type value sets.

Generalizes color/beam/focus palette building: each preset carries one or
more targets (fixture selections), each with its own attribute values. The
first target uses ``scope``; subsequent targets of the same preset merge
(per-fixture-type accumulation into one preset).

Args:
    preset_type: "color", "beam", "focus", "dimmer", "position", ...
    presets: list of {id, name?, by_target: [{target, attrs}]} where target
        is a selection command (e.g. "Fixture 101 Thru 128") and attrs is a
        list of [attribute, value] pairs.
    scope: "global" (default), "selective", or "universal".
    merge: if True the first target also merges (extend an existing preset).
    label: apply each preset's name as its label.

Returns:
    str: Operation result message

Examples:
    - Beam strobe across types: preset_type="beam", presets=[{"id":3,"name":"Strobe","by_target":[{"target":"Fixture 401 Thru 428","attrs":[["SHUTTER",50]]},{"target":"Fixture 201 Thru 215","attrs":[["MASTERSHUTTERSTROBE",21]]}]}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
preset_typeYes
presetsYes
scopeNoglobal
mergeNo
labelNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full burden. It discloses merging behavior, scope usage, and return type, but omits destructive effects, authorization needs, or rate limits. Adequate but incomplete.

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 summary, explanation, Args, Returns, and Examples. It is somewhat lengthy but each part earns its place. Minor opportunity to tighten.

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 (5 params, nested structures), the description covers behavior, parameters, and an example. Output schema exists, so return value explanation is sufficient. Lacks comparison to sibling tools.

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

Parameters5/5

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

Schema coverage is 0%, so description must compensate. It thoroughly explains each parameter, including the complex nested structure of 'presets', with examples. Adds significant meaning 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 starts with a clear verb-resource statement 'Build a preset palette of any type from per-fixture-type value sets.' It distinguishes itself from sibling tools like build_color_palette by generalizing across types.

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 explains the structure and behavior of presets, including how targets and merge work. It implies use for general palette building but lacks explicit when-not or alternative recommendations.

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