Skip to main content
Glama

store_preset

Save current programmer values to a preset. Merge into existing presets to add values without disturbing stored data for other fixture types.

Instructions

Store current programmer values as a preset.

Use merge to ADD the current selection's values into an existing preset
without disturbing values already stored for other fixture types (the
non-destructive way to extend a global palette to a new fixture group).

Args:
    preset_type: Preset type (dimmer, position, gobo, color, beam, focus, control, shapers, video)
    preset_id: Preset number
    scope: (Optional) Scope: "global", "selective", or "universal"
    merge: Merge into the existing preset (keeps other fixtures' stored values)
    overwrite: Overwrite the existing preset entirely

Returns:
    str: Operation result message

Examples:
    - Store color preset 1
    - Store global dimmer preset 5
    - Extend global color preset 7 to the current selection: merge=True

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
preset_typeYes
preset_idYes
scopeNo
mergeNo
overwriteNo

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 discloses that merge keeps existing values and overwrite replaces entirely, but it is unclear what happens if both flags are false (default). No mention of permissions, side effects, or error conditions. Adequate but not fully transparent.

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?

Description is concise and well-structured: starts with core purpose, then highlights a key use case, lists parameters with brief explanations, and includes examples. No unnecessary words, though the parameter list could be more compact.

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?

With 5 parameters and an output schema, the description covers the essential behavior (store, merge, overwrite). It explains the critical distinction between merge and overwrite. However, it does not elaborate on the meaning of each scope value (global vs selective vs universal), which would require domain knowledge. Overall sufficiently complete for the tool's complexity.

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 has 0% description coverage, but the description adds meaningful context: explains that 'merge' adds without disturbing, 'overwrite' replaces entirely, and 'scope' has options 'global', 'selective', or 'universal'. The parameter names alone are insufficient, but the description compensates well.

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?

Clearly states it stores programmer values as a preset. Distinguishes between merge (additive) and overwrite (replace), and provides a concrete use case for merging to extend a global palette. The verb 'store' and resource 'preset' are specific.

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?

Explicitly explains when to use merge (to add values to an existing preset without disturbing other fixtures) and implies overwrite for full replacement. However, it does not explicitly state scenarios where this tool is inappropriate or compare to siblings like 'store_cue'. The guidance on merge vs overwrite is helpful.

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