q-sys-mcp

Create or extend a change group

qsys_create_change_group

Create a change group to watch Q-SYS named controls and poll for changes. Add controls to an existing group for monitoring.

Instructions

Create a change group (or add Named Controls to an existing one) so you can poll for changes (ChangeGroup.AddControl).

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Change group id (any string; reused on poll)
`controls`	Yes	Named Control names to watch

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jun 22, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Without annotations, the description carries the full burden but only hints at behavior (e.g., 'reused on poll'). It does not disclose side effects, required permissions, error conditions, or what happens when the ID already exists beyond the implicit extension capability.

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 a single, front-loaded sentence that efficiently conveys the main action and intention. It contains no unnecessary words, though it could incorporate slightly more structural detail.

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?

For a simple tool with two required parameters and no output schema, the description covers the essential purpose but lacks information about return values, success/failure indicators, or common use cases. It is adequate but not fully comprehensive.

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%, with both parameters already described in the schema. The description adds minimal value by rephrasing the purpose ('add Named Controls to an existing one'), which aligns with the 'controls' parameter. However, it does not compensate beyond baseline.

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 explicitly states the tool's action ('Create a change group or add Named Controls to an existing one') and its purpose ('so you can poll for changes'). It distinguishes this tool from siblings like 'qsys_destroy_change_group' and 'qsys_poll_change_group' by focusing on creation/extension.

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?

No guidance is provided on when to use this tool versus alternatives such as 'qsys_change_group_add_component'. The description does not mention prerequisites, contexts, 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