GMA2 MCP

delete_group

Remove a fixture group permanently from the grandMA2 console. This destructive action deletes the group with no undo.

Instructions

Delete a fixture group (destructive).

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": {
      "group_id": "<group_id>"
    },
    "name": "delete_group"
  }
}

Input Schema

Name	Required	Description	Default
`group_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. While it mentions 'destructive', it does not elaborate on whether deletion is reversible, what happens to fixtures in the group, or if there are side effects on cues or sequences. The output schema exists but is not described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief (one phrase), which is concise but lacks necessary detail. It is front-loaded with the action and resource, but the brevity borders on under-specification. A moderate score of 3 reflects that it is not verbose, but could be improved.

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 single parameter, lack of annotations, and rich set of sibling tools, the description is incomplete. It does not explain the return value (despite an output schema existing), error states, or how the deletion affects related data. The agent lacks sufficient context to use this tool safely and effectively.

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 has only one parameter 'group_id' with no description, and schema description coverage is 0%. The tool description does not explain that 'group_id' is the identifier of the group to delete or how to obtain it. This leaves ambiguity for the AI agent.

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 verb 'delete' and the resource 'fixture group', with a parenthetical '(destructive)' that further distinguishes it as a dangerous operation. This differentiates it from sibling tools like 'create_fixture_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 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, such as when to delete a group versus modifying it. It does not mention prerequisites (e.g., the group must exist) or suggest alternative tools for non-destructive operations.

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

Deploy Server