X32/M32 MCP Server

Main Stereo Output Mute Control

main_mute

DestructiveIdempotent

Mute or unmute the main stereo output on an X32/M32 mixer, controlling the master output on/off state.

Instructions

Mute or unmute the main stereo output on the X32/M32 mixer. This controls the master output on/off state.

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": {
      "muted": "<muted>"
    },
    "name": "main_mute"
  }
}

Input Schema

Name	Required	Description	Default
`muted`	Yes	True to mute the main output, false to unmute

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.0Aug 9, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation trait is covered. The description adds minimal behavioral context beyond restating the action; it does not disclose side effects, but none are needed for a simple mute control.

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?

Two short sentences with no waste. Every word earns its place, and the most important information (action and target) is front-loaded.

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?

This is a simple one-parameter, no-output-schema tool. The description fully explains what the tool does and the parameter. No additional context is required.

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 description coverage is 100% for the single 'muted' parameter, which already explains its meaning. The description does not add additional parameter detail, so baseline 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 specific verbs ('Mute or unmute') and identifies the exact resource ('main stereo output on the X32/M32 mixer'). It clearly distinguishes from sibling tools like channel_mute and bus_mute by focusing on the main output.

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 for when to use this tool: whenever the main stereo output needs to be muted or unmuted. It does not explicitly mention exclusions or alternatives, but the resource specificity implies the appropriate use case compared to sibling tools.

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