gma3-mcp

Set cue timing

gma3_set_cue_timing

Edit the timing of an existing grandMA3 cue part by setting fade, delay, out-fade, out-delay, or snap-delay values in seconds; only supplied fields change and missing parts are refused.

Instructions

Edit the timing of an existing cue part (default part 0, the cue's main part) with one Set() per given field: fade (CueInFade), delay (CueInDelay), out_fade (CueOutFade), out_delay (CueOutDelay), snap_delay (SnapDelay), all in seconds; 0 is a value. Only the given fields are changed. Refuses (nothing sent) when the cue part does not exist. No command-line command is sent; selection and programmer are untouched. Reads the changed fields back from the part. Stored fixture values are not touched or verified. The mutation lock orders only this server's own mutations; it does not isolate the operation from another console operator or another client.

Input Schema

TableJSON Schema

Name	Required	Description
`cue`	Yes	One cue number, fractional allowed (2, 2.5, "10.001"; max three decimals). Ranges (Thru, +) are rejected.
`fade`	No	Cue (in) fade time in seconds; 0 is a value. Part property CueInFade.
`part`	No	Part number (default 0 = the cue's main part).
`delay`	No	Cue (in) delay time in seconds; 0 is a value. Part property CueInDelay.
`verify`	No	Read the result back after the mutation (default true). Verification is reported separately from the mutation steps.
`out_fade`	No	Out fade in seconds (dimmers going down); 0 is a value. Part property CueOutFade.
`sequence`	No	Sequence number (1..99999). Required unless use_selected_sequence is true; exactly one of the two.
`out_delay`	No	Out delay in seconds; 0 is a value. Part property CueOutDelay.
`snap_delay`	No	Snap delay in seconds (Part property SnapDelay); 0 is a value.
`use_selected_sequence`	No	Act on the console's currently selected sequence. It is resolved to its sequence number first, and the command is sent with that explicit number.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: only given fields mutate, nothing is sent on failure, no command-line command is issued, selection and programmer remain untouched, fixture values are not touched or verified, changed fields are read back, and it discloses the mutation-lock limitation (not isolated from other operators/clients). This is unusually candid behavioral detail.

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?

Front-loaded with the core action and the field list, and every sentence carries substantive information. It is dense and slightly run-on (many semicolon-joined clauses), which costs a point against a cleanly structured alternative, but there is little waste.

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?

For a 10-parameter mutation tool with no output schema, the description covers the mutation semantics, failure behavior, side-effect boundaries, the read-back/verify behavior, and the concurrency caveat. An agent has everything needed to invoke it 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?

Schema coverage is 100%, so the baseline is 3, but the description adds value by mapping each field to its console property (fade→CueInFade, out_delay→CueOutDelay, etc.) and stating the unit (seconds) and that 0 is a valid value. It does not cover cue/sequence selection semantics, but that is documented in the schema.

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?

States a specific verb (edit/Set) and resource (timing of an existing cue part) and enumerates the exact fields it operates on. It is clearly distinguishable from siblings like gma3_set_cue_trigger, gma3_store_cue, or gma3_set_property.

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?

Gives clear context: edits an EXISTING cue part, defaults to part 0, only supplied fields change, and it refuses when the part does not exist. It stops short of naming alternatives (e.g., store_cue_part for creation or set_cue_trigger), so the when-not guidance is contextually implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Set cue timing

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools