X32/M32 MCP Server

Channel Solo Control

channel_solo

Idempotent

Solo or unsolo an X32/M32 input channel, routing it to the solo bus for isolated monitoring.

Instructions

Solo or unsolo a specific input channel on the X32/M32 mixer. This routes the channel to the solo bus for isolated monitoring.

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": {
      "channel": "<channel>",
      "solo": "<solo>"
    },
    "name": "channel_solo"
  }
}

Input Schema

Name	Required	Description	Default
`solo`	Yes	True to solo the channel, false to unsolo
`channel`	Yes	Input channel number from 1 to 32

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.0Aug 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate this is a mutating, idempotent, non-destructive operation. The description adds the behavioral detail of routing the channel to the solo bus for isolated monitoring, which goes beyond the annotations. No contradictions with annotations.

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 two sentences, front-loaded with the action and resource, and every word earns its place. No redundancy or unnecessary details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 2-parameter tool with complete schema and annotations, the description fully covers purpose, effect, and usage context. No output schema needed for this action; the description is complete as-is.

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 'channel' and 'solo' fully described in the schema. The description adds minimal parameter-specific detail beyond stating 'specific input channel', so the baseline 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 uses a specific verb ('Solo or unsolo') with a clear resource ('specific input channel on the X32/M32 mixer'), and explains the function (routes to solo bus for isolated monitoring). This clearly distinguishes it from sibling tools like channel_mute or channel_set_volume.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context that this is for isolated monitoring via the solo bus, which implies when to use it. However, it does not explicitly state when not to use it or mention alternatives, so it stops short of a 5.

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