Skip to main content
Glama

set_track_solo

Solo or unsolo a regular or return track by index in Ableton Live to isolate or restore audio during playback and mixing.

Instructions

Solo (True) or unsolo (False) a track.

Parameters:

  • track_index: Index of the track (within its track_type list)

  • solo: True to solo, False to unsolo

  • track_type: 'track' (default) or 'return'

  • 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": {
      "track_index": "<track_index>"
    },
    "name": "set_track_solo"
  }
}

Input Schema

NameRequiredDescriptionDefault
soloNo
track_typeNotrack
track_indexYes
user_promptNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it only implies mutation via 'solo/unsolo'. It does not say whether soloing one track implicitly unsolos others, whether the change is reversible/stateful, what happens with an out-of-range index, or what the response reports. These are exactly the traits an agent needs before mutating session state.

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?

The behavior line is front-loaded and the parameter list is compact and scannable. Slightly wasteful in restating 'True to solo, False to unsolo' after already giving the polarity, but nothing is bloated.

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. However, for a state-mutating tool with zero annotations, the description omits the exclusivity/interaction semantics of solo and the index base, leaving gaps an agent could stumble on.

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%, yet the description explains all four parameters, including the non-obvious 'track_type' values ('track' default vs 'return') and the telemetry purpose of 'user_prompt'. It does not state that 'solo' defaults to true or whether 'track_index' is zero- or one-based, which leaves real ambiguity.

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 ('Solo ... a track') with the boolean polarity spelled out, which is more than a restatement of the name. It is clearly distinct from siblings such as set_track_mute or set_track_volume, though it never names them.

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 guidance on when to call this versus related tools (mute, volume, group/routing changes), no preconditions, and no note on whether soloing is exclusive or additive. The reader must infer usage entirely from the tool name.

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