Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

swing_clip

Destructive

Delays off-beat 8th or 16th notes in a Session MIDI clip by a grid-relative amount to add groove or triplet feel. For Ableton Live's own grooves, use set_clip_groove.

Instructions

Swing a Session MIDI clip: delay off-beat 8ths (or 16ths) by amount (0..1 of the grid; 0.33 ≈ triplet feel). For Live's own grooves use set_clip_groove.

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_index": "<clip_index>"
    },
    "name": "swing_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
gridNo1/8
amountNo
clip_indexYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description implies note positions are rewritten. However, it does not say whether repeated application compounds the delay, whether the change is undoable, or whether it applies to the whole clip versus a region — meaningful gaps for a destructive mutation.

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 sentences, zero filler, and the core effect plus its unit of measurement come first. The sibling pointer is placed at the end where it belongs.

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?

An output schema exists, so return values need no explanation, and the destructive nature is covered by annotations plus the implicit note rewrite. What is missing is scope and repeat-application behavior, the main risks when calling a destructive transform.

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 coverage is 0%, so the description must carry the load, and it does for the two non-obvious parameters: 'amount (0..1 of the grid; 0.33 ≈ triplet feel)' and grid as 8ths or 16ths. track_index and clip_index are left undefined, but their meaning is self-evident from the naming.

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?

Names a specific verb and resource ('Swing a Session MIDI clip') and immediately explains the mechanism: delaying off-beat 8ths/16ths by a fraction of the grid. It also names the sibling it is not (set_clip_groove), so the agent can distinguish it without opening a schema.

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?

Explicitly routes the agent to set_clip_groove for Live's built-in grooves, which is the most likely confusion point among siblings like quantize_clip or humanize_clip. It stops short of stating preconditions (clip must be a Session MIDI clip with notes) or what happens on a non-MIDI/empty clip.

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