Skip to main content
Glama

Create setlist runner

create_setlist_runner

Builds a wall-clock setlist player for VJ shows, auto-advancing through sequenced visuals with crossfades or hard cuts, and optional HUD overlay.

Instructions

Layer-1 wall-clock setlist player for rehearsed VJ shows. Pass rows[] of (source TOP, duration_seconds, transition_seconds) and the tool builds a baseCOMP containing N Select TOPs (one per row), a Switch TOP, a Cross TOP for crossfaded boundaries (hard cut when transition_seconds=0), an optional NOW/NEXT/remaining Text TOP HUD composited over the program, a Timer CHOP + CHOP Execute engine that auto-advances rows on wall-clock time, and live custom params Play/Row/Skip/Prev/Loop/Defaulttransition for stage overrides. Output is a Null TOP at <parent>/<name>/out. Fills the gap between create_clip_launcher (manual grid) and create_cue_sequencer (musical bars).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsYesOrdered setlist rows. Each row: { source, duration_seconds, transition_seconds }.
sources_mapNoOptional `{ logical → TOP path }` to allow human-readable row sources like 'actA' instead of an absolute path.
default_transitionNoFallback `transition_seconds` (in seconds) for rows that omit it.
loopNoWhen the last row ends: wrap to row 0 (true) or stop (false).
autostartNoStart playing immediately on build.
show_hudNoBuild the NOW/NEXT/remaining Text TOP HUD as a child output.
nameNoEngine container name.setlist
parent_pathNoParent COMP path where the engine COMP is created (e.g. '/project1')./project1
Behavior4/5

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

Annotations show it is not read-only, not destructive, and open-world. The description adds substantial behavioral detail: it builds a baseCOMP with specific subcomponents, creates an output Null TOP, and includes live custom params for overrides. This is more than sufficient beyond the annotations.

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 detailed but well-structured, front-loading the purpose and rows usage, then listing built components and output. While it could be slightly trimmed, every sentence adds value and it is not overly verbose.

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 (8 params, nested objects, no output schema), the description covers the overall function, input structure, built components, output location, and live parameters. It also distinguishes from siblings. Minor omissions include error behavior or performance notes, but it is largely complete.

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?

The input schema already has 100% parameter descriptions, but the description adds meaning by explaining that rows define the setlist with source, duration, and transition, and maps to the built components. It also explains the default_transition and loop fallback behavior.

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 creates a layer-1 wall-clock setlist player for VJ shows, specifies the resources it builds (baseCOMP, Select TOPs, Switch TOP, etc.), and explicitly distinguishes itself from sibling tools create_clip_launcher and create_cue_sequencer.

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 indicates use for rehearsed VJ shows and differentiates from manual grid (clip launcher) and music-aligned sequencer, providing clear context. However, it does not explicitly list when not to use it or prerequisites.

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