Skip to main content
Glama

Manage cue

manage_cue

Manage named snapshots of custom parameters: store, recall, list, delete, and morph between them with timed crossfades. Optionally snap scene changes to beat or bar boundaries.

Instructions

Live-performance scene system: store / recall / morph / list / delete named cues (snapshots of a COMP's custom-parameter values). Unlike manage_presets, a cue can be reached with a timed morph that crossfades every numeric control from the current look to the cue over N seconds (eased), via a small Execute DAT — so you can glide between looks on stage instead of hard-cutting. Recall and morph also take an optional quantize ('beat'/'bar') that defers the change to the next musical boundary (from the project tempo) so scene changes land on the downbeat. Build cues with create_control_panel, then jump or morph between them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesstore a cue (snapshot of the COMP's custom params), recall it instantly, morph to it over time, list, or delete.
comp_pathNoCOMP whose custom-parameter values the cue captures (a control-panel container)./project1
nameNoCue name (required for store/recall/morph/delete).
durationNo(morph) Crossfade time in seconds from the current look to the cue.
quantizeNo(recall/morph) Snap the scene change to the music. 'off' (the default) fires immediately. 'beat' defers the recall/morph until the next beat boundary; 'bar' until the next bar (measure) boundary — read from the project tempo (op('/').time.tempo) and time signature. The change is scheduled, not blocking.
Behavior4/5

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

Annotations indicate non-readonly and non-destructive behavior. The description adds valuable context: morph crossfades over N seconds, quantize defers to musical boundaries, and changes are scheduled non-blocking. This information goes beyond annotations and aids agent understanding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph. It includes necessary information but lacks structuring (e.g., bullet points). It front-loads the core purpose but could be more succinct and organized for quick parsing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is provided, so the description should cover return values. It explains morph and recall behavior well but does not specify what 'list' or 'delete' returns or details about error conditions. For a complex tool with multiple actions, it is fairly complete but has gaps.

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 description coverage is 100%, so baseline is 3. The description adds meaningful extra context, especially for quantize (explains musical boundary deferral) and morph (crossfade behavior). This enriches understanding beyond schema descriptions.

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 is a live-performance scene system for managing cues with specific actions (store, recall, morph, list, delete). It distinguishes itself from the sibling 'manage_presets' by highlighting the timed morph feature, providing clear purpose and differentiation.

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 provides usage context by comparing to manage_presets and explaining when to use morph versus recall, including the optional quantize parameter for musical timing. It doesn't explicitly list when not to use other sibling tools, but the differentiation is clear.

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/Pantani/tdmcp'

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