Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fire_clip

Starts playback of a specified clip by track and clip index in Ableton Live, enabling AI-driven session control.

Instructions

Start playing a clip.

Parameters:

  • track_index: The index of the track containing the clip

  • clip_index: The index of the clip slot containing the clip

  • 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>",
      "clip_index": "<clip_index>"
    },
    "name": "fire_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_indexYes
track_indexYes
user_promptNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds almost nothing behavioral beyond that: it does not say what happens if the target slot is empty, whether firing a clip stops other clips on the same track, or whether playback is quantized. The only extra context is that user_prompt exists for telemetry.

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?

The purpose sentence is front-loaded and the parameter block is short and scannable, with no filler. The list format is justified given the zero schema coverage, though each entry mostly restates the parameter name.

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 values need not be explained, and the tool itself is conceptually simple. However, for a playback-triggering tool the description leaves out indexing conventions, empty-slot behavior, and interaction with other playing clips, which are the details an agent actually needs.

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

Parameters3/5

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

Schema description coverage is 0%, so the description carries the full burden, and it does list all three parameters. It usefully clarifies that clip_index is a slot index within a track, but it omits indexing base (0- vs 1-based), whether return/master tracks are counted, and what telemetry means for the user_prompt field. Partial compensation for a fully undocumented schema.

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?

States a specific verb and resource: 'Start playing a clip.' An agent knows the action is clip playback. It does not distinguish itself from close siblings such as fire_scene, start_playback, or stop_clip, so a reader must infer the slot-level scope from the parameter list rather than the prose.

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?

There is no when-to-use or when-not guidance. Nothing says to use this instead of start_playback (transport) or fire_scene (scene launch), nor does it mention prerequisites such as needing a clip already present in the slot. Usage is only implied by the parameter names.

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