Skip to main content
Glama

Create scene timeline

create_scene_timeline

Construct a scrubbable show timeline with ordered scenes, each recalling a stored cue on a target COMP. Playback is driven by a Timer-CHOP playhead with controls for Play, Pause, Stop, Seek, Rate, and Loop.

Instructions

Build a scrubbable show timeline: a single Timer-CHOP playhead drives ordered scenes that recall cues on a target COMP. Sits above create_cue_sequencer (beat-quantized) and create_scheduler (event-firing) as the show's master clock. Exposes Play/Pause/Stop/Seek/Rate/Loop/Active_Scene custom pars + a playhead Null CHOP (t_seconds, t_norm, scene_idx, scene_t). Consumes the foundation setlist schema: when setlist_path is given, each scene's setlist_slot is mirrored into tdmcp_scenes for downstream tools. Bars→seconds conversion uses BPM 120 + 4 beats-per-bar at build time (no auto-rescale on tempo change).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoCOMP that owns the cues (tdmcp_cues). Store scenes' cues first with manage_cue./project1
scenesYesOrdered scene list (sorted by `start` at build time). Overlaps drive morphs.
unitsNoInput unit for `start`/`duration`/`morph_in_seconds`. 'bars' is converted to seconds at build time using BPM 120 + 4 beats-per-bar (no auto-rescale on tempo change).seconds
loopNoEnd of last scene → wrap to 0.
rateNoPlayback rate multiplier (Timer CHOP speed). Exposed as a live custom par.
autoplayNoPulse the Timer's start on cook when true.
setlist_pathNoOPTIONAL path to a DAT holding the foundation-setlist JSON. When present, scene.setlist_slot is stored alongside each scene in tdmcp_scenes for downstream tools.
nameNoEngine COMP name.scene_timeline
parent_pathNoParent path where the engine COMP lives./project1
Behavior4/5

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

Adds behavioral details beyond annotations: explains bar-to-seconds conversion fixed at build, exposure of custom pars and playhead Null CHOP. Annotations already indicate non-readonly and non-destructive, so description supplements well.

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?

Front-loaded with core purpose and hierarchy, then technical details. Slightly verbose but each sentence adds value. Could be trimmed slightly, but remains clear.

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

Completeness5/5

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

Fully covers what the tool does, its outputs (exposed pars, Null CHOP), and behavioral constraints. No output schema, but description compensates. Sibling list is large, but description clearly differentiates.

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?

With 100% schema coverage, baseline is 3. The description adds context for several parameters (e.g., setlist_path triggers side effects, units conversion behavior). Does not repeat schema but enhances understanding.

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 verb 'Build' and the resource 'scrubbable show timeline', distinguishing it from siblings like create_cue_sequencer and create_scheduler by positioning it as the 'master clock'.

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 names alternatives and their characteristics (beat-quantized vs event-firing) and implies when to use this tool as the overarching timeline. Mentions prerequisite to store cues via manage_cue. Lacks explicit 'when not to use' but sufficient context.

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