Skip to main content
Glama
Sign In
AbletonMCP

AbletonMCP

by juampicosta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_automation_envelope

Remove an automation envelope from a clip in Ableton Live by specifying track, slot, and envelope indices.

Instructions

Completely remove an automation envelope from a clip.

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>",
      "slot_index": "<slot_index>",
      "envelope_index": "<envelope_index>"
    },
    "name": "delete_automation_envelope"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_indexYes
slot_indexYes
envelope_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

The description says 'completely remove' but does not disclose whether the operation is irreversible, what permissions are needed, or the effect on the clip. With no annotations provided, the description should convey such behavioral traits; it fails to do so adequately.

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

Conciseness3/5

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

The description is a single sentence, concise and front-loaded. However, it could include additional information (e.g., parameter hints) without becoming overly verbose, so it is adequate but not optimal.

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

Completeness1/5

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

Given the tool has 3 required parameters, no annotations, and an output schema, the description is severely lacking. It omits parameter semantics, usage guidelines, and behavioral context, making it incomplete for effective agent invocation.

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

Parameters1/5

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

The input schema has 3 parameters (track_index, slot_index, envelope_index) with 0% description coverage. The description does not mention any parameters, so it adds no meaning beyond the schema. For a tool with no schema descriptions, the description should compensate but does not.

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?

The description 'Completely remove an automation envelope from a clip' uses a specific verb 'remove' and names the resource 'automation envelope from a clip'. It distinguishes from sibling tools like 'clear_automation_envelope' and 'remove_automation_point' by implying full deletion rather than clearing or point removal. However, it could be slightly more explicit about the difference.

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 is provided on when to use this tool versus alternatives like 'clear_automation_envelope' or 'remove_automation_point'. The description lacks usage context or prerequisites, leaving the agent to infer when deletion is appropriate.

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