GMA2 MCP

set_executor_fader

Adjust an executor's fader level to a specific percentage from 0 to 100, giving precise control over lighting output intensity.

Instructions

Set an executor's fader level.

Args:
    executor_id: Executor number
    value: Fader value (0-100)

Returns:
    str: Operation result message

Examples:
    - Set executor 1 fader to 75%

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": {
      "executor_id": "<executor_id>",
      "value": "<value>"
    },
    "name": "set_executor_fader"
  }
}

Input Schema

Name	Required	Description	Default
`executor_id`	Yes
`value`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are present, so the description must fully disclose behavior. It omits details on side effects (e.g., whether it overrides a running cue), required permissions, or state changes beyond setting the fader level. The return type is mentioned but not fully explained.

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 and front-loaded with the purpose. The Args, Returns, and Examples sections are structured clearly with no wasted words. Every sentence adds value.

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, the description covers core functionality and parameters adequately. The output schema exists but is not detailed; the description mentions a result message. Some additional context about executors and fader effect would improve completeness, but it's sufficient for a basic setter.

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 0% as the schema only provides titles and types. The description adds meaningful context: executor_id is 'Executor number' and value is 'Fader value (0-100)', including a range. This goes beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 resource 'executor's fader level', making the purpose unambiguous. It distinguishes from sibling tools like set_executor_rate or set_executor_speed by specifying the fader level, but does not explicitly differentiate.

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 is provided on when to use this tool versus alternatives such as control_executor or flash_executor. The description lacks context about prerequisites or use cases, leaving the agent to infer.

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

Deploy Server