X32/M32 MCP Server

Set Channel EQ Band

channel_set_eq_band

Idempotent

Configure an EQ band on an X32/M32 input channel. Adjust frequency, gain, or quality for bands 1 to 4.

Instructions

Configure a specific EQ band on an input channel. The X32/M32 has 4 parametric EQ bands per channel.

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>",
      "band": "<band>",
      "parameter": "<parameter>",
      "value": "<value>"
    },
    "name": "channel_set_eq_band"
  }
}

Input Schema

Name	Required	Description
`band`	Yes	EQ band number from 1 to 4
`value`	Yes	Parameter value (range depends on parameter type)
`channel`	Yes	Input channel number from 1 to 32
`parameter`	Yes	EQ parameter: f=frequency(Hz), g=gain(dB), q=quality/width

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.2.0Aug 9, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With annotations already indicating this is a non-read-only, non-destructive, idempotent operation, the description adds the useful context of the hardware having 4 parametric EQ bands. It does not, however, describe side effects, reversibility, or any additional behavioral traits beyond the 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 primary action, and contains no redundant information. Every word adds value, making it highly concise 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 simple setter tool, the description is largely complete given the rich schema and annotations. It explains the tool's purpose and hardware context, while the schema covers all parameters. The only minor gap is that it does not mention how to determine appropriate value ranges, but that is partially addressed by the schema's parameter descriptions.

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 each parameter already having a description and an enum for 'parameter'. The description adds minimal extra meaning about the parameters, only reinforcing the band range via the 4-band mention. The baseline of 3 is appropriate as schema carries the semantic load.

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 it configures a specific EQ band on an input channel, using the verb 'Configure' and the resource 'EQ band'. It also mentions the X32/M32's 4 parametric bands, which further distinguishes it from sibling tools like channel_set_volume or channel_set_gain.

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 its use for EQ band configuration but does not explicitly state when to choose it over alternatives or mention any exclusions. The context about 4 bands hints at valid usage but lacks explicit guidance on when to use this tool vs similar channel_set tools.

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