Skip to main content
Glama

set_track_solo

Solo or unsolo a specified track or return track by index, letting you isolate audio during mixing and arrangement.

Instructions

Solo or unsolo a track.

Parameters:

  • track_index: The track

  • solo: true solos, false unsolos

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

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>",
      "solo": "<solo>"
    },
    "name": "set_track_solo"
  }
}

Input Schema

NameRequiredDescriptionDefault
soloYes
track_typeNotrack
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only restates that this is a mutation ('solo or unsolo'). It does not disclose whether soloing one track clears other solos, whether the operation is idempotent, or what happens for an invalid index; the output schema covers return values, but the mutation semantics remain undisclosed.

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 sentence is front-loaded and the parameter list is compact with no filler. Slightly more structure (e.g., a note on solo exclusivity) could be added without bloat, but nothing present is wasted.

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 three-parameter mutation with an output schema, the description covers inputs adequately and need not explain returns. It is still thin on behavioral context an agent needs before calling, notably solo exclusivity and index semantics, which matters given the absence of annotations.

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 0%, so the description must compensate, and it does document all three parameters, including the default 'track' and the 'return' alternative for track_type. However, track_index is described only as 'The track', leaving indexing convention (zero-based? arrangement order?) unexplained.

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?

States a specific verb (solo/unsolo) and resource (a track) in the first line, which is enough to distinguish it from sibling mutators like set_track_mute or set_track_arm. It stops short of naming a sibling or contrasting behavior, so it is clear but not maximally differentiated.

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 at all: nothing says when to solo versus mute, whether soloing is exclusive (a common DAW behavior), or what happens when unsoloing an already-unsoloed track. The agent must infer everything 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.

Deploy Server

Other Tools