ableton-mind

Overview Schema Source Related Servers Discussions Admin

create_midi_clip

Create an empty MIDI clip in a specified track and clip slot, with configurable length and optional name. Use when you need a new clip in a known slot.

Instructions

Create an empty MIDI clip in a session clip slot. Use when the target MIDI track and clip slot are known and a new clip is needed. NOT idempotent for occupied slots; wrapped in an undo step and verified by returned clip length/name.

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>",
      "clip_slot_index": "<clip_slot_index>",
      "length_beats": "<length_beats>"
    },
    "name": "create_midi_clip"
  }
}

Input Schema

Name	Required	Description	Default
`track_index`	Yes
`clip_slot_index`	Yes
`length_beats`	Yes
`name`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses non-idempotence, undo step, and verification by returned clip length/name. However, it does not specify what happens when slot is occupied (error or overwrite) or other side effects, leaving some ambiguity.

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?

Three sentences, front-loaded with action and usage. Efficient but could be slightly more structured; e.g., separating usage from behavioral notes.

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?

Adequate for a simple tool with 4 parameters and no output schema. Covers core purpose and key behavior but misses parameter explanations and error handling details. Not fully complete.

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

Parameters2/5

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

Schema coverage is 0%, so description should compensate. It only indirectly mentions 'name' via verification, but does not explain track_index, clip_slot_index, or length_beats. No parameter details are added beyond the schema.

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 action: 'Create an empty MIDI clip in a session clip slot.' It uses a specific verb and resource, and distinguishes from sibling tools like clip_add_notes or clip_fire by focusing on creation of a new empty clip.

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

Usage Guidelines5/5

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

Explicitly states when to use: 'Use when the target MIDI track and clip slot are known and a new clip is needed.' It also implies when not to use by noting non-idempotence for occupied slots, providing clear guidance.

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