GMA2 MCP

temp_executor

Temporarily activate a grandMA2 executor by its ID, with optional page-qualified addressing for lighting console control.

Instructions

Temporarily activate an executor (Temp).

Args:
    executor_id: Executor number
    page: Optional page number for page-qualified addressing

Returns:
    str: Operation result message

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>"
    },
    "name": "temp_executor"
  }
}

Input Schema

Name	Required	Description	Default
`executor_id`	Yes
`page`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

C2.4/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 disclose behavioral traits. 'Temporarily activate' is vague—does it destructively change state? Is it safe? There is no mention of side effects, return value meaning, or permissions. The description lacks transparency.

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 concise: 4 lines with the main purpose upfront. It efficiently states the action and parameters without extraneous text. While it could be expanded, it is not verbose.

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

Completeness2/5

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

Given the tool's complexity among many executor tools, no annotations, and an output schema declared, the description fails to provide necessary context. It does not explain the concept of temporary activation, how it interacts with other executor states, or what the return string means. The description is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It adds minimal semantics: 'executor_id: Executor number' and 'page: Optional page number for page-qualified addressing'. It does not explain valid ranges, the concept of page-qualified addressing, or how to use the parameters effectively.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Temporarily activate an executor', specifying a verb and resource. However, among sibling tools like flash_executor, top_executor, stomp_executor, etc., it does not differentiate what 'temporarily activate' means compared to them, making the purpose somewhat ambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no context for scenarios. It fails to help an agent decide between this and similar executor tools.

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

Deploy Server