Skip to main content
Glama
LiveSession MCP
by Uri-Rosen

set_sidechain

Routes a named track into an Ableton Compressor's sidechain input and turns S/C On, so you can set up ducking from AI control. Works only with Compressor devices.

Instructions

Route a track (by name, e.g. "Drums") into a Compressor's sidechain input and switch S/C On. Live's API routes sidechains only into Compressor (not Glue Compressor, Gate or Auto Filter).

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>",
      "source": "<source>"
    },
    "name": "set_sidechain"
  }
}

Input Schema

NameRequiredDescriptionDefault
enableNo
sourceYes
track_typeNotrack
device_nameNo
track_indexYes
device_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare this is a non-read-only but non-destructive local operation. The description adds useful behavioral detail that it both routes the track and switches S/C On, and that only Compressor supports sidechain routing, but it does not explain reversibility, what enable=false does, or how device selection is resolved.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tightly written sentences with the primary action front-loaded and the device limitation immediately following. There is no redundant or filler wording.

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?

It covers the core purpose and the most important device constraint, and the output schema can explain return values. But for a six-parameter mutation with zero schema descriptions, it is incomplete regarding parameter roles and device-targeting behavior.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, so the description must carry the burden. It only hints that the source is a track by name and that the destination is a Compressor; it does not explain track_index, device_name, device_index, track_type, or enable, leaving most parameter meaning undocumented.

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 description states a specific action: routing a track into a Compressor sidechain input and switching S/C On. It also clarifies the supported device scope by excluding Glue Compressor, Gate, and Auto Filter, though it does not explicitly distinguish itself from broader routing tools like set_routing.

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 an important when-not constraint: sidechains only work with Compressor, not the named alternatives. However, it does not explain when to use this tool versus set_routing or set_device_param, nor does it describe prerequisites such as selecting the target device.

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