Skip to main content
Glama

update_device

Modify an Ableton Live device, rack chain, or Drum Rack pad by changing only specified settings such as power, name, position, macros, variation, mute, or solo in one undoable step.

Instructions

Turn a device on or off, rename it, move it to another track or chain, set a rack's visible macros, store or recall a macro variation, or mute and solo a rack chain or Drum Rack pad. Only given fields change. One undo step.

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": {
      "target": "<target>"
    },
    "name": "update_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
onNoDevice on: true / false. Empty: unchanged.
muteNoFor a chain or pad: true / false.
nameNoNew device name.
soloNoFor a chain or pad: true / false.
indexNoWith move_to: position from 0. Empty: at the end.
targetYesDevice, rack chain or Drum Rack pad address. Examples: t0/d0 (first device on t0), t1/d0/c1/d0 (first device in chain 1 of that rack), t2/d0/pC1 (Drum Rack pad C1), rA/d0, m/d0
move_toNoMove into this track or chain: t2, t0/d0/c1.
variationNoFor a rack: store, or a variation number to recall.
visible_macrosNoFor a rack: how many macro knobs to show.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnly=false, destructive=false, idempotent=false), and the description adds real value on top: 'Only given fields change' documents partial-update semantics and 'One undo step' discloses undo coalescing. What's missing is whether an invalid or conflicting field causes the whole call to fail and what the call returns.

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 with the capability list, then two short constraint sentences with no filler. The capability clause is dense and comma-heavy, but every clause maps to a real parameter group.

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?

For a nine-parameter multi-purpose tool with no output schema, the description covers the operation space and undo behavior but leaves open whether operations can be combined, what happens on conflict, and what the response contains. Adequate but with clear gaps.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains each field, and the description's clause 'Only given fields change' usefully reinforces the empty-string default. However, it adds no cross-field dependency detail beyond the schema, such as that index only applies with move_to or that mute/solo only apply to chains and pads.

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?

Uses specific verbs paired with specific resources (turn on/off, rename, move, set visible macros, store/recall variation, mute/solo) and names the target entity types (device, track, chain, Drum Rack pad). The scope is unambiguous, though it never distinguishes itself from plausible siblings like configure_device or set_device_params.

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?

The enumeration of capabilities implies when the tool applies, and 'Only given fields change' hints at partial updates, but there is no explicit guidance on when to choose this over configure_device, set_device_params, or update_track, and no statement about whether multiple operations can be combined in a single call.

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