Dim all theatrical lights to black over a configurable duration, defaulting to 3 seconds, for clean scene endings and cue transitions.
Fade all lights to black (turn off)
| Name | Required | Description | Default |
|---|---|---|---|
| fadeOutTime | No | Time in seconds to fade out (default: 3.0) |
Changes observed during successful MCP inspections.
v1.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does convey that the effect is global ('all lights'), but it says nothing about reversibility (undo), interaction with running cue lists or playback, or what happens to the current active look.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with the core action front-loaded and zero filler. It is very brief, but appropriately so for a simple one-argument tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple (one optional param, no output schema), so the bar is low, but the description omits any behavioral detail about undo/restoration or how it interacts with active cues and looks. Adequate but leaves real gaps for a state-changing global operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the fadeOutTime parameter (default 3s) is fully documented in the schema. The description adds only that a fade occurs, which the schema parameter name already implies. Baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb and resource: 'Fade all lights to black', which an agent can distinguish from sibling tools like activate_look or next_cue. It does not explicitly name a sibling it contrasts with, but the action is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as activate_look or stop_cue_list. The agent must infer from the name alone that this is a global blackout operation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.