Skip to main content
Glama

set_track_volume

Adjust a track, return, or master fader volume in Ableton Live using normalized 0.0–1.0 values, where 0.85 is 0 dB and 0.0 is silence.

Instructions

Move a track's fader.

Parameters:

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

  • volume: Fader position 0.0–1.0 (0.85 is 0 dB, 0.0 is silence)

  • 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>",
      "volume": "<volume>"
    },
    "name": "set_track_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
volumeYes
track_typeNotrack
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry behavior itself, and it does contribute real domain context: the fader's 0.0–1.0 range, that 0.85 equals 0 dB, and that 0.0 is silence. It does not say whether the change is persistent, undoable, whether automation modes override it, or whether a live connection is required for a mutation, which is a notable gap for a write tool with zero annotation coverage. Return values are covered by the output schema, so their absence here is acceptable.

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?

A one-line purpose followed by a tight parameter list is well front-loaded and wastes no words. The list format is slightly redundant with a structured schema, but it is the right shape for compensating for a 0%-coverage 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 three-parameter mutation tool with an output schema and no annotations, the definition covers addressing modes, the value scale, and defaults. What is missing is behavioral context around mutation side effects such as persistence, undo, or automation interaction, which would round it out.

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%, so the description must compensate entirely, and it does: every one of the three parameters is explained, including the meaning of the volume scale with a dB reference point, the accepted track_type values with a stated default, and the conditional irrelevance of track_index for the master type. This adds genuine meaning the bare schema cannot convey.

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 opening sentence, "Move a track's fader," pairs a specific verb with a specific resource and clearly separates this tool from siblings such as set_track_panning or set_track_mute. It never names an alternative explicitly, but the operation itself is unambiguous.

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 only implied: an agent can infer this is the tool for setting fader level, and the note that track_index is "ignored for 'master'" hints at addressing modes. There is no statement of when to prefer this over related tools (e.g. automation vs. static level) and no prerequisites or exclusions.

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