Skip to main content
Glama

set_device_sidechain

Routes a Compressor's sidechain from another track and turns it on or off, so you can duck bass or pads with the kick.

Instructions

Feed a Compressor's sidechain from another track (e.g. duck the bass or pads with the kick) and switch its sidechain on. source is the name of the track as Live lists it (see get_device_info: sidechain.available_types), channel e.g. "Post FX" / "Pre FX". Live's API exposes sidechain routing on the Compressor; other devices with a sidechain (Gate, Glue, Auto Filter...) are routed in the interface.

Parameters:

  • track_index / device_index: The Compressor

  • source: Sidechain source track name (exact, or a unique part of it)

  • channel: Source tap (optional)

  • enable: Turn the sidechain on (default) or off

  • track_type: "track", "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>",
      "device_index": "<device_index>",
      "source": "<source>"
    },
    "name": "set_device_sidechain"
  }
}

Input Schema

NameRequiredDescriptionDefault
enableNo
sourceYes
channelNo
track_typeNotrack
track_indexYes
device_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the API-level restriction and that `enable` toggles sidechain on/off, but says nothing about failure behavior when `source` doesn't match a track, whether existing routing is replaced, or permission/undo implications of mutating device 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?

Front-loaded purpose sentence, then a compact parameter list; each line carries information. The parenthetical device examples and the API-limitation sentence both earn their place, though the prose is slightly denser than necessary for a tool of this size.

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?

An output schema exists, so return values need no explanation, and the description covers purpose, platform restriction, and every parameter for a 6-parameter mutation tool. The remaining gap is error/edge-case behavior, which is the only thing an agent might still need.

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%, and the description compensates almost fully by documenting all six parameters: which indices identify the Compressor, that `source` takes an exact or uniquely-matching name, that `channel` is an optional source tap with examples ("Post FX"/"Pre FX"), the `enable` default, and the `track_type` values ("track"/"return"/"master"). This adds meaning well beyond the bare typed schema.

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?

States a specific verb and resource ('Feed a Compressor's sidechain from another track... switch its sidechain on') with a concrete use case (duck bass/pads with kick). It also bounds scope by naming the one device type this API path supports, so an agent can tell it apart from the generic set_device_parameter and get_device_info siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear when-to-use case and a genuine when-not: sidechain routing via the API only works on the Compressor, while Gate/Glue/Auto Filter must be routed in the Live interface. It also points at get_device_info (sidechain.available_types) to discover valid sources. No explicit sibling alternative is named for setting the same routing by other means, so this stops short of a 5.

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