X32/M32 MCP Server

Get Parameter (Low-Level)

get_parameter

Read-onlyIdempotent

Retrieve current parameter values from X32/M32 mixers via raw OSC address patterns for debugging or accessing parameters not covered by standard tools.

Instructions

ADVANCED/LOW-LEVEL TOOL: Retrieves current parameter values from X32/M32 mixer using raw OSC address patterns. Consider using semantic tools (channel_*, bus_*, etc.) for common operations. Use this tool for parameters not covered by semantic tools or for debugging purposes.

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": {
      "address": "<address>"
    },
    "name": "get_parameter"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	OSC address pattern for the parameter to read (e.g., "/ch/01/mix/fader" for channel 1 fader level, "/main/st/mix/fader" for main stereo fader, "/ch/01/eq/1/f" for channel 1 EQ band 1 frequency)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.0Aug 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating safe, non-mutating behavior. The description adds context about being low-level and using raw OSC patterns, which is not present in the annotations. It does not contradict annotations and contributes useful behavioral insight beyond the structured hints.

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 with no filler. It leads with a clear warning ('ADVANCED/LOW-LEVEL TOOL') and immediately states function and usage guidance. Every sentence earns its place, making it highly efficient and well-structured.

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?

For a low-level read tool with one parameter, no output schema, and strong annotations, the description covers purpose, usage, and parameter semantics. It could have explained what the returned value looks like, but given the simplicity and the openWorldHint, the provided information is adequate for an agent to use the tool correctly.

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 input schema fully describes the single 'address' parameter with 100% coverage, including examples. The description text itself does not add parameter-specific meaning beyond indicating raw OSC usage, which is already in the schema. The schema carries the semantic weight, so the baseline of 3 applies.

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 tool retrieves current parameter values from X32/M32 mixers via raw OSC address patterns. It explicitly differentiates itself from semantic siblings by labeling itself as ADVANCED/LOW-LEVEL, making the purpose and resource unambiguous.

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

Usage Guidelines5/5

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

Provides explicit guidance: 'Consider using semantic tools (channel_*, bus_*, etc.) for common operations' and 'Use this tool for parameters not covered by semantic tools or for debugging purposes.' This clearly states when to use the tool and when to prefer alternatives.

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