GMA2 MCP

stop_effects

Stop all running effects for selected fixtures by removing effect values from the programmer.

Instructions

Stop all running effects for the current selection.

Removes effect values from the programmer using the Off command.

Returns:
    str: Operation result message

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stop_effects"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions using the 'Off command', but does not disclose side effects (e.g., whether it affects only programmer values or also fixture states), required permissions, or whether the operation is reversible. Minimal behavioral context beyond the core action.

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?

Two precise sentences: the first states the primary purpose, the second describes the mechanism. No redundant information. Efficiently front-loaded.

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 (no parameters, straightforward action), the description is largely complete. It includes a return type, though no output schema is shown. Could briefly mention which effects are stopped (all? selected?) but current content suffices for a simple tool.

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?

The tool has zero parameters, so the description needs no parameter explanations. Baseline is 4, and the description adequately covers the operation without needing to reference parameters.

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?

Description clearly states 'Stop all running effects for the current selection' and elaborates with 'Removes effect values from the programmer using the Off command.' This provides a specific verb and resource, distinguishing it from sibling tools like apply_effect or sync_effects_tool.

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

Usage Guidelines3/5

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

The description implies usage for stopping effects on the current selection, but does not explicitly state when to use this tool versus alternatives (e.g., sync_effects_tool, apply_effect) or provide when-not-to-use scenarios. No guidance on prerequisites or context.

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

Deploy Server