Skip to main content
Glama
Sign In
Ableton Copilot

Ableton Copilot

by F-Fischer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_device

Remove a specific instrument or effect from an Ableton Live track using track and device indices. Clean up your mix by deleting unwanted devices.

Instructions

Delete a device (instrument or effect) from a track.

Parameters:

  • track_index: The index of the track the device is on

  • device_index: The index of the device on the track

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

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

Input Schema

NameRequiredDescriptionDefault
track_indexYes
user_promptNo
device_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description must fully convey behavioral traits. It only says 'Delete' without disclosing irreversibility, side effects, permission requirements, or response behavior, leaving the destructive nature under-specified.

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 compact: a one-sentence purpose statement followed by a concise parameter list. Every element serves a purpose and is front-loaded.

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?

The description covers the basic operation and all parameters, but omits critical invocation details like whether track_index and device_index are zero-based, and does not mention any return or error behavior. This leaves meaningful ambiguity for a deletion tool.

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 description coverage is 0%, but the description enumerates all three parameters with brief semantic explanations, including the telemetry role of user_prompt. This adds meaningful context beyond the bare titles, though index base/constraints are not specified.

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 clearly states the tool deletes a device (instrument or effect) from a track. This specific verb+resource scope distinguishes it from sibling tools like delete_track and delete_clip.

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?

The description provides no guidance on when to use this tool versus alternatives such as delete_track or delete_clip, and no preconditions or exclusions are mentioned.

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