GMA2 MCP

create_fixture_group

Create a group from a range of fixtures and assign an optional name. Saves the selection as a new group for lighting control.

Instructions

Create a group containing a specified range of fixtures.

This tool selects the specified range of fixtures and saves them as a group.
Optionally, a name can be assigned to the group.

Args:
    start_fixture: Starting fixture number
    end_fixture: Ending fixture number
    group_id: Group number to save
    group_name: (Optional) Group name, e.g., "Front Wash"

Returns:
    str: Operation result message

Examples:
    - Save fixtures 1 to 10 as group 1
    - Save fixtures 1 to 10 as group 1 with name "Front Wash"

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": {
      "start_fixture": "<start_fixture>",
      "end_fixture": "<end_fixture>",
      "group_id": "<group_id>"
    },
    "name": "create_fixture_group"
  }
}

Input Schema

Name	Required	Description	Default
`start_fixture`	Yes
`end_fixture`	Yes
`group_id`	Yes
`group_name`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The description explains that the tool selects a range of fixtures, saves them as a group, and optionally assigns a name. It also mentions the return type. However, it does not disclose whether overwriting an existing group is possible, which is a behavioral gap. Since no annotations are provided, the description carries full burden but is only partially transparent.

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 a clear summary, detailed explanation, parameter listing, and examples. It is concise and front-loaded, with no unnecessary sentences.

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 has 4 parameters and returns a string message. The description covers the core functionality and provides examples, but lacks details on edge cases like overwriting existing groups or behavior when invalid fixture numbers are provided. It is adequate for basic use but incomplete for comprehensive understanding.

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?

The schema coverage is 0%, meaning no descriptions in the schema. The description's 'Args:' section restates the parameter names and types almost verbatim from the schema, adding minimal additional meaning. For example, 'start_fixture: Starting fixture number' does not provide context beyond the parameter name.

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 clearly states the tool's purpose: 'Create a group containing a specified range of fixtures.' It uses a specific verb and resource, and is easily distinguishable from sibling tools like delete_group or list_groups.

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 provides examples that imply usage scenarios (e.g., saving fixtures 1-10 as a group with an optional name), but does not explicitly state when to use this tool versus alternatives or mention any prerequisites or exclusions.

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

Deploy Server