Ableton MCP Extended

by zabolotniydj

Overview Schema Source Related Servers Discussions Admin

Python

Local

disable_device

Bypass a device on a specific track by providing its index or name, with optional chain index for racks.

Instructions

Disable (bypass) a device on a track.

Parameters:

track_index: Track number (1-based).
device_index: Device number (1-based). Use 0 if using device_name.
device_name: Device name (alternative to device_index).
chain_index: Chain number inside a rack (1-based, 0 = no chain).

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

Input Schema

Name	Required	Description	Default
`chain_index`	No
`device_name`	No
`track_index`	Yes
`device_index`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 21, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action (disable/bypass) but offers no information on side effects, reversibility, permissions, or how the device state changes beyond being disabled. The description is too sparse to give the agent confidence about consequences or prerequisites.

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 extremely concise and well-structured: a one-sentence purpose followed by a bulleted parameter list with inline details. Every sentence and bullet adds value, and the format is front-loaded with the primary action. Zero waste.

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?

For a 4-parameter tool with an output schema, the description covers the essential information needed to invoke the tool: purpose, parameter semantics, and defaults. It does not mention edge cases (e.g., device not found, track missing) or prerequisites, but these are secondary. Given the presence of an output schema, return values need not be detailed, and the description is sufficiently complete for most uses.

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?

The description adds essential meaning to each parameter, including 1-based indexing for track_index and device_index, the use of 0 for device_index when device_name is provided, and the chain_index default. This goes beyond the bare schema, which only lists titles with no descriptions, and compensates for the 0% schema description coverage. It is clear, though it could be slightly more explicit about parameter precedence.

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 description opens with a specific and unambiguous purpose: 'Disable (bypass) a device on a track.' This clearly identifies the verb (disable/bypass), the resource (device on a track), and semantically distinguishes the tool from siblings like enable_device (opposite) and delete_device (removal). No tautology or vagueness.

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 description implies usage context—disabling or bypassing a device—but does not provide explicit when-to-use vs. when-not-to-use guidance or mention alternatives such as enable_device or delete_device. With sibling tools available, an agent could infer intent, but no exclusions or tricks are given, so it earns a middle score.

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

Deploy Server