Skip to main content
Glama

configure_tracks

Batch-apply changes to Ableton Live tracks, returns, and master in one call: update names, colors, volume, pan, mute/solo, and routing without separate requests.

Instructions

Apply many track changes in ONE call (much faster and cheaper than one call per setting). Each item is a dict with track_index and any of: track_type ('track'|'return'|'master'), name, color, volume_db, volume, pan, mute, solo, output (routing destination name). Example: [{"track_index": 0, "name": "Kick", "color": "red", "output": "DRUMS BUS", "volume_db": -6}] Items are applied in order; a failing item does not stop the rest.

Parameters:

  • changes: List of per-track change dicts

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

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": {
      "changes": "<changes>"
    },
    "name": "configure_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYes
user_promptNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose two important traits: items are applied in order and a failing item does not abort the rest. It says nothing about permissions, whether changes are undoable, or how failures are reported back, leaving real gaps for a mutation tool.

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 with the value proposition, then the schema shape, then an example. The trailing 'Parameters:' block partly restates inline content, but the user_prompt telemetry note earns its place.

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

Completeness4/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 not be described, and the description covers ordering and partial-failure behavior for a nested batch payload. Only the error surface and value-range details for numeric fields are missing.

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 coverage is 0% and 'changes' is an untyped object array, so the description must compensate — and it does list the accepted keys including the track_type enum and a worked example. However, it does not explain semantics for ambiguous fields such as volume vs. volume_db (ranges, units) or track_index addressing, so it remains partial.

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

Purpose5/5

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

States a specific verb and resource ('Apply many track changes') plus the key differentiator: batch vs. one-call-per-setting. The list of mutable attributes makes the scope concrete enough to distinguish it from single-property tools like set_device_parameter.

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

Usage Guidelines4/5

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

Explicitly recommends this over 'one call per setting,' which gives the agent a clear selection rule for batch edits. It stops short of naming a specific sibling alternative or stating exclusions (e.g., when a single targeted call is preferable).

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