Skip to main content
Glama

Create panic control

create_panic

Build a live-performance safety control with instant blackout and freeze switches to protect VJ visuals. Wraps any video source in a panic button for instant kill or frame hold.

Instructions

Build a live-performance safety control — the 'oh no' button every VJ needs. Wraps a source in a small COMP with two instant kill switches: Blackout forces the output to black (a Level TOP's brightness1 driven to 0) and Freeze holds the last frame (a Cache TOP stops capturing, active → 0). With an input_path the source is pulled in by a Select TOP (so it can live in another container); without one a built-in Ramp TOP test source is used so it builds and previews standalone. Output is a Null TOP. Big Blackout / Freeze toggle buttons are exposed on the container so a performer can hit them instantly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
input_pathNoOptional absolute path of the live source TOP to protect. Pulled in via a Select TOP (TD wires can't cross containers, so it's referenced by path). If omitted, a built-in test source (Ramp TOP) is used so the panic COMP still builds and previews on its own.
blackoutNoInitial Blackout state. When on, the output is forced to black (Level TOP brightness1 = 0) — the instant kill switch.
freezeNoInitial Freeze state. When on, the last frame is held instead of passing the live input (Cache TOP stops capturing — active = 0).
expose_controlsNoExpose big Blackout and Freeze toggle buttons on the container so a performer can hit them instantly.
parent_pathNo/project1
Behavior4/5

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

Discloses creation of a COMP with specific internal logic (Level TOP, Cache TOP, Select TOP, Ramp TOP). Annotations (readOnly=false, destructiveHint=false) are consistent. No contradictions.

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 well-structured and informative, with key details upfront. Slightly long but every sentence adds value.

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?

Explains output (Null TOP) and internal components, suitable for a tool that creates a component. No output schema, but return behavior is sufficiently implied.

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?

Adds meaningful context for input_path, blackout, freeze, and expose_controls beyond schema descriptions. Parent_path lacks description, but overall coverage is high (80%+).

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 uses specific verbs ('build', 'wraps') and clearly identifies the resource ('live-performance safety control', 'oh no button'). It distinguishes this from sibling create_ tools by detailing the unique blackout and freeze functionality.

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 context on when to use input_path vs standalone, and describes the tool's role as a safety control. However, it does not explicitly compare to sibling tools or state when not to use it.

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