GMA2 MCP

set_effect_speed

Adjust the speed of lighting effects for the current selection by specifying a value in BPM or hertz.

Instructions

Set the effect speed for the current selection.

Args:
    value: Speed value
    unit: Speed unit — "bpm" (beats per minute) or "hz" (hertz)

Returns:
    str: Operation result message

Examples:
    - Set effect speed to 120 BPM
    - Set effect speed to 2.5 Hz

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "value": "<value>"
    },
    "name": "set_effect_speed"
  }
}

Input Schema

Name	Required	Description	Default
`value`	Yes
`unit`	No		bpm

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It only describes inputs and return type, but does not state if the operation is destructive, requires permissions, or has side effects (e.g., overwriting existing speed).

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 with Args, Returns, and Examples sections. It is concise but includes necessary details. However, the Args section partially duplicates schema info; could be more streamlined.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with 2 parameters and an output schema. The description covers inputs, return type, and examples. However, it lacks context on what 'current selection' entails (e.g., multiple fixtures, effect types) and any dependencies (e.g., an active effect).

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 adds significant meaning: it explains that 'value' is a speed number, 'unit' can be 'bpm' or 'hz' (not an enum in schema), and notes default 'bpm'. This clarifies usage beyond the raw 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?

The description states 'Set the effect speed for the current selection' with a clear verb ('Set') and resource ('effect speed'), and specifies scope ('current selection'). Among sibling tools like set_effect_phase, set_effect_range, etc., this uniquely identifies the purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. The description does not mention prerequisites, when-not-to-use, or contrast with related tools like set_effect_speed_group or set_effect_seconds.

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

Deploy Server