OSC MCP Server

osc_set_channel_source

Assign an input source to a specific channel on digital mixers like Behringer X32 or Midas M32, enabling flexible audio routing and signal management.

Instructions

Set the input source for a 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>",
      "source": "<source>"
    },
    "name": "osc_set_channel_source"
  }
}

Input Schema

Name	Required	Description	Default
`channel`	Yes	Channel number (1-32)
`source`	Yes	Source number (0-63)

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?

No annotations are provided, so the description carries full burden. It states a mutation action ('Set'), implying changes to the system, but doesn't disclose behavioral traits such as required permissions, side effects, error conditions, or what happens if invalid values are used. This is inadequate for a mutation tool with zero annotation coverage.

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 that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, with zero waste.

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 lacks details on behavioral aspects like safety, permissions, or return values, which are crucial given the tool's complexity and the absence of structured data to compensate.

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 descriptions for 'channel' and 'source' including numeric ranges. The description adds no additional meaning beyond the schema, such as explaining what a 'source' represents or how changes affect the system. Baseline 3 is appropriate when 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 ('input source for a channel'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'osc_set_channel_name' or 'osc_get_channel_source', which would require more specificity about what distinguishes setting a source from other channel operations.

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. With siblings like 'osc_get_channel_source' for reading and various other 'osc_set_' tools for different parameters, the description lacks context on appropriate use cases or exclusions.

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

Deploy Server