Skip to main content
Glama
whybothercoding

Ableton Live MCP Server

by whybothercoding
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_device

Read-onlyIdempotent

Reads a device's parameters, chains, drum pads, and macro state, returning addresses, values, ranges, and labels so you can inspect or modify Live devices.

Instructions

Read a device with all its parameters (index, address, value, min, max, display as Live shows it, default, value_items labels for quantized ones, is_enabled) and, for racks, its chains, return chains, occupied drum pads (each with the addresses of the devices it holds) and macro state. address: 'tracks/2/devices/0', 'returns/0/devices/1', 'master/devices/0' or nested 'tracks/2/devices/0/chains/1/devices/2' (a name selector works too: 'tracks/2/devices/name:EQ Eight'). Device names per track are in describe_set. Change a parameter with set_properties on its address ('.../parameters/5' or '.../parameters/name:Frequency', field value; a quantized parameter also takes its label such as 'Low-pass'); many at once with items. Devices also have properties (name, on, collapsed) and racks chains, pads and mixers have theirs: see list_properties. Simpler, Wavetable, Drift, Meld, Eq Eight, Looper, Hybrid Reverb, Roar, Spectral Resonator, Shifter, Drum Cell and plug-ins also have their own properties and methods: the result's specific block lists them (choices such as a wavetable or voice mode are properties that take the label the device shows; ..._options lists the labels), and a Simpler's sample is at '/sample'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesA device, e.g. 'tracks/2/devices/0'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds substantial context about the result shape (the `specific` block for plugin devices, where a Simpler's sample lives). It does not discuss pagination or performance, but discloses what the read returns beyond the annotations.

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

Conciseness2/5

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

The read purpose is front-loaded, but the paragraph then drifts into detailed set_properties mechanics (value field, quantized labels, `items`) that belong to the sibling tool, not to a read definition. Several sentences about other tools don't earn their place here, making the description bloated and hard to parse.

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?

With no output schema and a simple one-param input, the description carries the return-shape burden and does so thoroughly (parameter fields, chains, pads, macros, `specific` block). It is more than complete for the tool's complexity, even if over-broad.

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

Parameters4/5

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

Schema coverage is 100% with a single `address` param, so baseline is 3; the description goes beyond the schema's one-line example by giving literal forms (tracks/2/devices/0, returns/0/devices/1, master/devices/0, nested chains) and the name selector syntax ('name:EQ Eight').

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 opening verb+resource is precise: 'Read a device with all its parameters...' and it enumerates the scope (parameters, chains, return chains, drum pads, macro state) so an agent can distinguish it from get_properties/list_properties. The address examples make the target unambiguous.

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?

It routes related tasks to siblings explicitly: 'Change a parameter with set_properties', 'see list_properties' for properties, and 'Device names per track are in describe_set'. It doesn't state when NOT to use get_device, but the alternative routing is clear.

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