Skip to main content
Glama

set_track_panning

Set panning for an individual, return, or master track using -1.0 left to 1.0 right values to control stereo placement in the mix.

Instructions

Pan a track.

Parameters:

  • track_index: The track (ignored for "master")

  • panning: -1.0 hard left, 0.0 centre, 1.0 hard right

  • track_type: "track" (default), "return" or "master"

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": {
      "track_index": "<track_index>",
      "panning": "<panning>"
    },
    "name": "set_track_panning"
  }
}

Input Schema

NameRequiredDescriptionDefault
panningYes
track_typeNotrack
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden and mostly does not meet it. It never says whether the change is real-time, whether it is undoable, what happens if panning is sent for a track that does not exist, or how master panning interacts with track_index. Only the master-ignores-track_index quirk is disclosed.

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?

Front-loaded one-line purpose followed by a compact parameter list; no filler sentences. The bullet list format is easy to scan, though the mixed prose/list style is slightly informal.

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?

An output schema exists, so return values need no explanation and the simple setter nature keeps the bar low. Still, with no annotations at all, the description should say something about persistence, undo, or real-time effect to be fully adequate.

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

Parameters4/5

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

Schema description coverage is 0%, and the description compensates well: it defines the numeric panning range (-1.0 to 1.0 left/right), enumerates the three track_type values with the default, and notes the track_index special case for master. This adds meaning the raw schema lacks (no enum, no min/max). Only the integer vs. named-index convention for track_index is left unclear.

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 first line states a specific verb and resource ("Pan a track"), so the action is unambiguous. It does not distinguish itself from siblings like set_track_volume or set_track_solo, though the parameter list makes the resource focus obvious.

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?

Usage is implied rather than stated: the track_type values ("track", "return", "master") describe the scope of applicability and note that track_index is ignored for master, which is genuine selection guidance. There is no explicit when-to-use or when-not clause and no named alternative.

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

Deploy Server

Other Tools