OSC MCP Server

osc_set_eq_frequency

Adjusts the equalizer frequency for a specific channel band on digital mixers like Behringer X32 and Midas M32 to fine-tune audio output.

Instructions

Set EQ frequency for a channel band

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>",
      "frequency": "<frequency>"
    },
    "name": "osc_set_eq_frequency"
  }
}

Input Schema

Name	Required	Description
`channel`	Yes	Channel number (1-32)
`band`	Yes	EQ band (1-4)
`frequency`	Yes	Frequency in Hz

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose whether this is a destructive write operation (implied by 'Set'), what permissions are needed, if changes are immediate or require confirmation, or any error conditions. The description adds no context beyond the basic action.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and target, making it easy to parse quickly.

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

Completeness2/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 annotations and no output schema, the description is incomplete. It doesn't explain what happens on success/failure, return values, or side effects. Given the complexity of audio mixing tools and lack of structured safety hints, more context is needed.

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%, with clear parameter descriptions and ranges in the schema. The description adds no additional meaning about parameters beyond what's in the schema (e.g., how frequency interacts with band or channel). Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Set') and target ('EQ frequency for a channel band'), which is specific and unambiguous. It distinguishes from siblings like 'osc_set_eq' (which likely sets broader EQ parameters) and 'osc_set_eq_q' (which sets Q factor), though it doesn't explicitly name these alternatives.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'osc_set_eq' or 'osc_set_eq_q', nor any context about prerequisites (e.g., EQ must be enabled). The description only states what it does, not when or why to invoke it.

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

Deploy Server