Skip to main content
Glama
Sign In
q-sys-mcp

q-sys-mcp

by reowens
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Clear a change group

qsys_change_group_clear

Remove all controls from a Q-SYS change group without deleting the group, enabling efficient reuse of the change group for new control sets.

Instructions

Remove all controls from a change group without destroying it (ChangeGroup.Clear).

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": {
      "id": "<id>"
    },
    "name": "qsys_change_group_clear"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesChange group id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It clarifies that the group is not destroyed, which is key behavioral info. However, it does not disclose potential side effects, required permissions, or behavior on non-existent groups.

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 a single concise sentence that is front-loaded with the action. Every word adds value, with no wasted text.

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 (one parameter, no output schema), the description adequately covers the core functionality and the key nuance of preserving the group. Missing details about error handling or empty groups are minor gaps.

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

Parameters3/5

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

Schema coverage is 100% and the parameter 'id' has a description in the schema. The tool description does not add additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 action 'Remove all controls from a change group' and the resource 'change group'. It explicitly distinguishes from destroying the group by saying 'without destroying it', which differentiates it from sibling tool qsys_destroy_change_group.

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 clearing all controls while preserving the group, but does not explicitly state when to use this tool versus alternatives like qsys_change_group_remove (which removes individual controls). No prerequisites or conditions are mentioned.

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

Deploy Server

Other Tools