Skip to main content
Glama

Create cue sequencer

create_cue_sequencer

Build a bar-quantized cue sequencer that advances through steps on beat boundaries, recalling or morphing stored cues on a target COMP for musical timing.

Instructions

Build a bar-quantized cue timeline: a Beat CHOP (on the global tempo) + a CHOP Execute DAT that, on each bar (or beat) boundary, advances through an ordered list of steps and recalls — or morphs over morph_seconds — that step's cue on a target COMP. The deterministic, musically-timed counterpart to create_autopilot (which is random/cyclic). Reuses manage_cue's stored cues and the same cue_morph engine, so store the target's cues with manage_cue first. Live Active / Step / BarsPerStep controls let you pause, jump, or retune on stage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoCOMP whose stored cues (tdmcp_cues, from manage_cue) the sequencer recalls/morphs. Store the cues first./project1
stepsYesThe ordered timeline: each step names a cue and how many bars/beats it holds before the next.
loopNoWhen the last step finishes, wrap back to the first (true) or stop (false).
quantizeNoUnit each step's count is measured in: 'bar' (× the project's beats-per-bar) or raw 'beat'.bar
morph_secondsNo0 = snap to each cue instantly on its boundary; >0 = crossfade to it over this many seconds (via the same cue_morph engine manage_cue uses).
nameNoName of the engine container built inside target.cue_seq
parent_pathNoWhere to create the sequencer engine COMP./project1
Behavior4/5

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

Discloses that it creates internal components (Beat CHOP, CHOP Execute DAT) and reuses the cue_morph engine. No contradiction with annotations (readOnlyHint=false, destructiveHint=false). Adds context about quantize units and live controls.

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 a single, dense paragraph that efficiently conveys the core functionality. Could be more structured but remains concise and informative.

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 complexity of the tool and missing output schema, the description adequately explains the purpose and behavior. It mentions live controls and reuse of existing cues, though post-creation interaction could be more detailed.

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

Parameters3/5

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

Input schema covers 100% of parameters with individual descriptions. The tool description adds high-level context but does not provide significant new insights 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 clearly states it builds a bar-quantized cue timeline using specific components (Beat CHOP, CHOP Execute DAT). It distinguishes itself from the sibling create_autopilot by emphasizing deterministic, musically-timed 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?

Provides clear prerequisite: store cues with manage_cue first. Contrasts with create_autopilot, giving context for when to use this tool. Could be more explicit about when not to use it, but the distinction is effective.

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