Ardour Ultra MCP

Overview Schema Source Related Servers Discussions Admin

set_track_pan

Idempotent

Set a track's stereo pan position using a signed normalized value from -1 (left) to +1 (right), with 0 centered, to control its azimuth in an Ardour session.

Instructions

Set stereo azimuth in signed normalized units -1..+1.

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": {
      "request": "<request>"
    },
    "name": "set_track_pan"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Description	Default
`data`	No
`error`	No
`success`	No
`warnings`	No
`revision_after`	No
`changed_objects`	No
`revision_before`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond restating the value range—it says nothing about the dry_run, confirm_delete, or expected_revision (optimistic concurrency) parameters that materially change how the call behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no filler. It is efficient, though its brevity is achieved by omitting useful context rather than by tight editing of rich content.

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?

An output schema exists, so return values needn't be explained, but this is a mutation tool whose request object carries four nested fields, two of which (confirm_delete, expected_revision) imply meaningful transactional semantics. A single sentence about azimuth is not enough for an agent to call it correctly in all cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% at the top level, and while the nested `pan` property carries a description, `dry_run`, `confirm_delete`, and `expected_revision` are undocumented in both schema and description. The description repeats only the pan range, so it does not compensate for the coverage gap on a multi-field request object.

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 pairs a specific verb ("Set") with a specific resource ("stereo azimuth" / track pan) and names the value domain -1..+1, which distinguishes it from siblings like set_track_gain or set_track_mute. It does not explicitly name those siblings, but the resource is unambiguous.

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?

There is no when-to-use guidance, no prerequisites, and no mention of how this differs from adjacent tools such as set_track_gain or set_group_properties. The agent must infer that this is the pan-specific setter purely from the name.

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

Deploy Server