Skip to main content
Glama

Create show failover

create_show_failover

Build a live-show failover watchdog that switches from a primary source to a fallback when cook stalls or errors occur, with configurable crossfade and auto-recover.

Instructions

Build a live-show watchdog: a Switch TOP (blend=1 cross-dissolve) between a primary source TOP (NDI/camera/Spout/Syphon path, or a synthetic noiseTOP when none is given) and an MP4 fallback (or a constantTOP when no file is given), driven by an Info CHOP + watchdog CHOP-Execute DAT that trips on cook stall (total_cooks delta stays flat for stall_ms) and, optionally, primary cook errors. A Filter CHOP smooths the integer Switch index into a fade_ms crossfade. Sticky-recover auto-returns to primary after recover_ms healthy; otherwise stays on fallback until Reset. Exposes Active / Stall_Ms / Fade_Ms / Sticky_Recover / Reset / Force_Fallback controls and a Null CHOP of status channels for bind_to_channel. Returns the container, output TOP, status CHOP, control names, and the operator paths.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
primary_pathNoAbsolute TD path to the primary source TOP (NDI/camera/Spout/Syphon/any TOP). Empty → builds a synthetic noiseTOP so the network is offline-safe.
fallback_fileNoFilesystem path to the fallback MP4 / still. Empty → a constantTOP (dark grey) is used as a safe fallback.
stall_msNoConsecutive ms of zero cook progress before failover trips.
fade_msNoCrossfade duration in ms (0 = hard cut). Drives the Filter CHOP that smooths the Switch TOP index.
sticky_recoverNoWhen true, auto-switch back to primary after `recover_ms` of healthy cooking. When false, stays on fallback until Reset is pressed.
recover_msNoHealthy duration before auto-recover (only used when sticky_recover=true).
watch_errorsNoAlso trip on primary cook errors (`errors > 0`), not just on stall.
status_overlayNoComposite a small LIVE/FALLBACK badge (textTOP + compTOP) into the output.
parent_pathNoWhere to create the show_failover system container./project1
Behavior5/5

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

Description comprehensively explains behavior: failover triggers (stall or errors), crossfade smoothing, sticky-recover logic, control exposure, and return values. Annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) are consistent, and description adds significant context.

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 dense and informative, front-loading the purpose. While somewhat lengthy, each sentence adds value and avoids redundancy. Could be slightly more concise without losing detail.

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?

Despite 9 parameters and no output schema, the description fully explains the system, controls, and return values. It covers all relevant aspects for an agent to invoke correctly.

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?

All 9 parameters are documented in schema (100% coverage). The description adds value by explaining parameter interactions (e.g., recover_ms depends on sticky_recover) and providing context 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 it builds a 'live-show watchdog' with specific failover logic (primary source, fallback, stall detection, crossfade). It distinguishes from siblings by detailing unique failover mechanisms.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied for live shows needing automatic failover, but no explicit when-to-use vs alternatives or when-not-to-use. Among siblings like create_live_source or create_video_player, this tool is specific but guidance is absent.

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