Skip to main content
Glama

set_track_volume

Set a track, return, or master fader level in Ableton Live using dB or a normalized value to control mix volume.

Instructions

Set a track's fader. Prefer volume_db (e.g. -6.0); volume is the raw normalized fader value 0.0-1.0 (0.85 is 0 dB in Live).

Parameters:

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

  • volume_db: Target level in dB (-inf to +6)

  • volume: Raw normalized fader value, used only if volume_db is not given

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

  • 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_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
volumeNo
volume_dbNo
track_typeNotrack
track_indexYes
user_promptNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does add real domain context that annotations could not supply — the 0.0-1.0 normalized scale, that 0.85 corresponds to 0 dB in Live, and the dB ceiling of +6 — but it says nothing about failure modes for an invalid track_index, whether the change is immediate or audible, or any permission/undo behavior for this mutation.

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 lead sentence front-loads the core action and the parameter preference, followed by a tight bulleted list. It is appropriately sized, with only minor redundancy in restating the parameter names that already exist in the schema.

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?

For a five-parameter mutation tool with zero schema coverage, the description is nearly sufficient — all parameters are explained, precedence is defined, and the unit mapping is spelled out. It stops short only on error conditions and the effect on an out-of-range track_index; return values need not be covered since an output schema exists.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description documents every one of the five parameters: track_index scoping (relative to its track_type list), volume_db units and range, volume's normalized scale and its precedence rule, track_type's three allowed values with the default, and the telemetry purpose of user_prompt. This is meaning the schema does not provide.

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?

The description opens with a precise verb+resource, "Set a track's fader," which is unambiguous and clearly distinct from adjacent siblings such as set_track_pan, set_track_mute, or set_track_color. An agent can identify the operation without opening the schema.

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?

It gives a clear preference rule between the two value parameters ("Prefer volume_db") and states the conditional use of volume, but it never says when to reach for this tool versus alternatives, nor does it mention prerequisites like needing a valid track index or an existing track. Usage is implied by the operation name rather than explicitly framed.

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