Skip to main content
Glama

set_cue_timing

Set fade, delay, out-fade, and out-delay timing on a cue or the current selection to control lighting transitions precisely.

Instructions

Set fade/delay timing on a cue or the current selection.

Provide any subset (at least one required). ``target`` applies the timing to
a specific object (e.g. "cue 5" or "cue 5 sequence 2"); omit to apply to the
current programmer selection.

Args:
    fade: Fade time (seconds)
    delay: Delay time (seconds)
    out_fade: Out-fade time (seconds)
    out_delay: Out-delay time (seconds)
    target: Optional target object string

Returns:
    str: Operation result message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fadeNo
delayNo
out_fadeNo
out_delayNo
targetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the operation as setting timing values, which implies modification, but does not disclose potential side effects, permissions, or error handling. It is adequate but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (under 100 words), front-loaded with the purpose, and structured with a parameter list and return type. Every sentence adds value without redundancy.

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?

Given the tool's simplicity (setting timing on cues) and the presence of an output schema, the description covers the main functionality, parameters, and return type. It could mention error handling or constraints on values, but it is sufficient for basic use.

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 0% schema description coverage, the description compensates by listing each parameter with a brief explanation (e.g., 'Fade time (seconds)'). It clarifies that at least one parameter is required and that 'target' is optional. However, it could provide more details like units for all parameters or typical value ranges.

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 verb 'Set' and the resource 'cue or the current selection', with a specific scope (fade/delay timing). It distinguishes itself from sibling tools like set_step_timing by explicitly mentioning cues.

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 that at least one parameter is required and clarifies how the 'target' parameter works (omit for current selection). It does not explicitly mention when not to use the tool or compare with alternatives like set_cue_cmd, but the context is clear enough for an agent.

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/chienchuanw/gma2-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server