Skip to main content
Glama

Create safety blackout chain

create_safety_blackout_chain
Destructive

Build a deterministic safety blackout chain for live shows: configurable fade-to-black with optional emergency snap, hotkey or watchdog trigger, and symmetric fade-in recovery. No Python at cook time.

Instructions

Build a live-show safety primitive at the very end of the master output chain: deterministic fade-to-black over a configurable time, optional emergency single-frame hard-cut, optional hotkey + external watchdog trigger, and symmetric fade-in recovery. All reactivity is parameter-driven (Speed + Lookup CHOP + Math/Logic CHOPs) — no Python runs at cook time, so the chain is ALLOW_EXEC=0-safe. Complements create_panic (per-source kill+freeze) by being the master-output dimmer with grace, recovery, and a watchdog hook. Returns the container, source, dim, emergency-gate, composite, and output node paths plus the trigger merge/target/speed/lookup nodes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_pathNoAbsolute path of the master TOP to protect. Pulled in via a Select TOP (TD wires can't cross COMPs). If omitted, a Ramp TOP test source is used so the chain still builds + previews.
parent_pathNoParent COMP the safety chain is built inside (default '/project1')./project1
fade_secondsNoTime the soft fade-to-black (and symmetric fade-in) takes. 0 = instant.
fade_curveNoInterpolation shape for the fade ramp, applied via a Lookup CHOP curve so the ramp is deterministic and Python-free at cook time.ease_in_out
initial_stateNoBoot state. 'live' = pass-through, 'black' = Blackout toggle on at load, 'held' = Hold toggle on (good for show open before first cue).live
arm_emergency_snapNoExpose an Emergency momentary pulse that bypasses the fade and hard-cuts to black.
hotkeyNoKeyboard In CHOP key spec that toggles Blackout (e.g. 'ctrl.b'). null/empty disables — hotkey is opt-in safe, requires a modifier.ctrl.b
watchdog_channelNoOptional absolute CHOP path + channel ('node:channel') — when non-zero, forces Blackout on. Lets external monitors trigger blackout deterministically without Python.
recovery_modeNoWhen the watchdog returns to 0: 'manual' keeps it black until the artist clears it; 'auto_on_clear' fades back in.manual
show_safe_labelNoOptional caption baked into the black frame (Text TOP composited over the dimmed output). Empty/null = no caption.SHOW SAFE
expose_controlsNoBuild the control panel with Blackout / Emergency / Fade Seconds / State LED.
Behavior5/5

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

The description discloses deterministic behavior, cook-time Python absence, and the nature of returning multiple node paths, which goes beyond the annotations ('readOnlyHint: false', 'destructiveHint: true', 'openWorldHint: true'). It adds valuable context about safety and reactivity without contradicting 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 a single, well-structured paragraph that front-loads the main purpose and key features. It is concise without omitting critical information, though it could benefit from slightly more structured formatting for readability.

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?

Given the tool's complexity (11 parameters, no output schema), the description is remarkably complete. It explains the return value (list of node paths), safety features, and relationship to sibling tools. It covers all essential aspects for an AI agent to understand its purpose and usage.

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 coverage is 100% with descriptions for all 11 parameters. The description adds context for key parameters like 'hotkey' (opt-in safe, requires modifier) and 'recovery_mode' (manual vs auto), enhancing understanding beyond schema alone. However, many parameters are already well-described in 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 live-show safety primitive at the master output chain, detailing specific features like deterministic fade-to-black, emergency snap, hotkey, watchdog, and recovery. It distinguishes from the sibling tool 'create_panic' by specifying it is the master-output dimmer with grace and recovery.

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 explains when to use this tool vs. alternatives by explicitly stating it 'complements create_panic' and positioning it as the master-output safety chain. It also highlights that it is parameter-driven and Python-free, guiding appropriate usage. Lacks explicit when-not-to-use statements.

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