Skip to main content
Glama

assign_appearance

Assigns a color appearance (frame/background) to grandMA2 pool objects or cues using RGB, HSB, hex, or by copying from another object, or resets to default.

Instructions

Assign an appearance (frame/background color) to a grandMA2 pool object or cue.

Colors can be specified via RGB (0-100), HSB (hue 0-360, sat/bright 0-100),
hex color string, or by copying from a source object. Use reset to clear.

Args:
    object_type: Object type (e.g., "group", "cue", "preset", "macro")
    object_id: Object number or compound ID (e.g., 1 or "0.1")
    end: (Optional) End ID for applying to a range of objects
    source_type: (Optional) Source object type to copy appearance from
    source_id: (Optional) Source object ID to copy appearance from
    reset: Reset appearance to default
    color: Hex color code (e.g., "FF0000") or gel name
    red: Red component (0-100)
    green: Green component (0-100)
    blue: Blue component (0-100)
    hue: Hue (0-360)
    saturation: Saturation (0-100)
    brightness: Brightness (0-100)

Returns:
    str: Operation result message

Examples:
    - Set group 1 to red: object_type="group", object_id=1, red=100, green=0, blue=0
    - Set preset 0.1 to hex color: object_type="preset", object_id="0.1", color="FF0000"
    - Copy appearance from macro 13 to macro 2: object_type="macro", object_id=2, source_type="macro", source_id=13
    - Reset group 1 appearance: object_type="group", object_id=1, reset=True

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_typeYes
object_idYes
endNo
source_typeNo
source_idNo
resetNo
colorNo
redNo
greenNo
blueNo
hueNo
saturationNo
brightnessNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It explains the operation (assign, copy, reset) and return type but does not disclose side effects (e.g., overwriting existing appearance) or permissions needed.

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 a clear purpose, then parameter details and examples. It is front-loaded and each sentence adds value, though the parameter list is lengthy due to tool complexity.

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?

Covers all parameters thoroughly, provides examples, and mentions return type. However, it lacks discussion of error cases or responses, and no output schema details are provided beyond the return string.

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?

With 0% schema description coverage, the description fully compensates. It explains all 13 parameters with types, ranges, examples, and optional usage, adding significant meaning beyond the bare 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 clearly states the tool assigns an appearance (frame/background color) to grandMA2 pool objects or cues. This specific verb-resource combination distinguishes it from sibling tools like apply_effect or build_color_palette.

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

Usage Guidelines3/5

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

The description provides examples but no explicit guidance on when to use this tool vs alternatives. Usage is implied by the narrow purpose, but the description does not cover prerequisites or exclusions.

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