Skip to main content
Glama
Sign In
Ableton Live 12 MCP

Ableton Live 12 MCP

by juancruzmunozalbelo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

live12_wavetable_modulation_matrix

Inspect, set, or clear modulation assignments and depths in Ableton Live 12 Wavetable's modulation matrix to control how sources shape target parameters.

Instructions

Inspects or updates modulation assignments in the Ableton Live 12 Wavetable modulation matrix.

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>",
      "action": "<action>"
    },
    "name": "live12_wavetable_modulation_matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesMatrix action: 'set' modulation depth, 'get' modulation depth, or 'clear' all matrix assignments.
amountNoModulation depth between -1.0 and 1.0.
sourceNoModulation source name (e.g. 'LFO 1', 'Env 2', 'Velocity', 'Modwheel').
targetNoTarget parameter name (e.g. 'Filter 1 Freq', 'Osc 1 Pos', 'Filter 1 Res').
track_indexYesZero-based track index.
device_indexYesZero-based index of the Wavetable device.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden, yet it does not say that 'clear' wipes all matrix assignments, that 'set' overwrites an existing assignment, what permissions or device state are required, or what happens on an invalid track/device index. It adds essentially no behavioral context beyond the title.

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 single front-loaded sentence with no filler, appropriately sized. It is terse but not padded, though its brevity comes at the cost of the missing detail scored elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter tool that can mutate device state with zero annotations and no output schema, the description should explain the set/get/clear semantics, index preconditions, and result behavior. Instead it is one sentence that leaves all of that to the schema.

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%, including an explicit enum meaning for action and ranges for amount, so the schema does the heavy lifting and a baseline 3 applies. The description itself contributes no additional parameter meaning (e.g., interaction between source/target and amount).

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?

Names a specific resource (Live 12 Wavetable modulation matrix) and the verbs (inspect/update), which is enough to distinguish it from unrelated siblings like live12_device_set_parameter or live12_rack_macro_control. However, the description omits the third capability 'clear' that the schema exposes, so it slightly under-describes the tool's own surface.

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

Usage Guidelines2/5

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

No guidance on when to prefer this over the generic live12_device_set_parameter or live12_lom_set, and no prerequisites stated (e.g., that track_index/device_index must point at an existing Wavetable device). The only usage-shaped information, the set/get/clear choice, lives in the schema, not the description.

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