Skip to main content
Glama

Create panic control

create_panic
Destructive

Build a live-performance safety control with instant kill switches: blackout forces output to black, freeze holds the last frame. Exposes toggle buttons for performers to cut video instantly.

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. Marked destructive because firing Blackout/Freeze disables the live output. Returns the container, the source/freeze/blackout/output node paths, and the initial toggle states.

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_pathNoParent COMP the panic container is built inside (default '/project1')./project1
Behavior5/5

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

The description provides extensive detail beyond annotations: explains the internal mechanism (Level TOP, Cache TOP, Select TOP), output as Null TOP, and return values. It confirms destructive behavior and clarifies what happens under the hood.

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 front-loaded, but slightly verbose. Every sentence adds value, though some technical details could be streamlined.

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 no output schema, the description covers return values and provides a comprehensive overview of tool behavior, parameter interactions, and use cases.

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, the description adds context like why input_path uses Select TOP and how blackout/freeze technically work, enhancing understanding without being essential.

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 tool's purpose as building a live-performance safety control with instant kill switches. It uses specific verbs like 'build' and 'wraps', and distinguishes itself from siblings like 'create_safety_blackout_chain' by focusing on dual kill switches and the 'oh no button' metaphor.

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 implies usage for live performance scenarios needing instant output freeze or blackout. It explains standalone vs. integrated usage with input_path, but does not explicitly mention when not to use or compare to specific alternatives.

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