Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_arrangement_clip

Creates an empty MIDI clip at a specified beat in Ableton Live's Arrangement view, returning its index so you can fill it with chords or melody via other tools.

Instructions

Create an empty MIDI clip directly in the Arrangement at beat start. Fill it with write_chords/write_melody(arrangement=True, clip_index=).

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>",
      "start": "<start>",
      "length": "<length>"
    },
    "name": "create_arrangement_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYes
lengthYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation. The description usefully adds that the result is an *empty* clip and how to fill it afterwards, but says nothing about preconditions (MIDI track required), behavior if start overlaps an existing clip, or unit assumptions for length.

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?

Two short sentences, zero waste, with the core action and the key differentiator ('directly in the Arrangement') front-loaded and the follow-up workflow immediately after.

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?

An output schema exists, so return-value explanation is unnecessary, and the reference to a returned clip_index is a helpful bridge. However, for a 3-required-parameter mutation with 0% schema coverage, the description leaves too much of the parameter contract and clip-conflict behavior unspecified.

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 description coverage is 0%, so the description must carry parameter meaning. It only clarifies that `start` is a beat position; `length` (units, beats vs seconds) and `track_index` (index into which ordering) are left undocumented in both schema and description.

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?

States a specific verb (create), resource (empty MIDI clip) and precise location (directly in the Arrangement at beat `start`). The 'Arrangement' qualifier distinguishes it from session-oriented siblings like create_clip, and 'MIDI' distinguishes it from create_audio_clip.

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

Usage Guidelines4/5

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

Gives clear follow-up guidance: use write_chords/write_melody with arrangement=True and clip_index=<returned index> to populate the clip, which tells the agent this tool is a two-step workflow opener. It does not explicitly contrast with create_clip or import_audio_to_arrangement, so the when-not guidance is implicit.

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