OSC MCP Server

osc_set_main_pan

Adjust the stereo pan position for the main left-right audio mix on digital mixers like Behringer X32 and Midas M32.

Instructions

Set the pan position for the main LR mix

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": {
      "pan": "<pan>"
    },
    "name": "osc_set_main_pan"
  }
}

Input Schema

Name	Required	Description	Default
`pan`	Yes	Pan position (-1.0 to 1.0)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 12, 2026

TDQS

B3.1/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 for behavioral disclosure. While 'Set' implies a write/mutation operation, the description doesn't mention whether this requires specific permissions, has side effects, or what happens if the operation fails. It provides minimal behavioral 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, clear sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the essential information and wastes no space on redundant or irrelevant details.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with 100% schema coverage and no output schema, the description provides the basic purpose but lacks important context. Without annotations and with many similar sibling tools, it should ideally clarify differentiation from alternatives and provide more behavioral context about this write operation.

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 the parameter 'pan' fully documented in the schema including its type, range, and description. The description doesn't add any parameter information beyond what's already in the schema, so it meets the baseline expectation but doesn't provide additional value.

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 resource ('pan position for the main LR mix'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this from sibling tools like 'osc_set_pan' or 'osc_set_aux_pan', which appear to perform similar pan-setting operations on different targets.

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 about when to use this tool versus alternatives like 'osc_set_pan' or 'osc_set_aux_pan'. The description only states what it does, not when it's appropriate or what distinguishes it from similar sibling tools.

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

Deploy Server