q-sys-mcp

Set component control values

qsys_set_component

Set control values in a Q-SYS component with optional ramping to adjust audio/video system parameters.

Instructions

Set one or more control values within a named component, each optionally ramped (Component.Set). This MUTATES the running/emulated system.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Component name
`controls`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jun 22, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description explicitly states mutation (MUTATES) and mentions optional ramping, which are helpful behavioral cues. However, with no annotations, it lacks details on idempotency, error behavior, or system state implications.

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 succinct with two sentences: one for purpose and one for behavioral note. No redundant phrases.

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 mutation tool with no output schema and multiple siblings, the description covers the main operation and mutation. However, it lacks context on required component existence, error handling, and return value.

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?

The description adds meaning by explaining ramp as optional and that controls is an array of one or more control-value pairs. However, with 50% schema coverage, it does not fully describe the properties within controls (e.g., what 'name' refers to within the component).

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 'set' and resource 'control values within a named component'. It mentions optional ramping and explicitly calls out that it mutates the system, which distinguishes it from read-only siblings like qsys_get_component.

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 that this tool is for setting one or more controls (vs. single control via qsys_set_control), but it does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives or prerequisites.

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

Deploy Server