Skip to main content
Glama
romanstark

Live Maestro

by romanstark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

stop

Idempotent

Halt Ableton Live transport playback, and optionally end all playing Session clips. Choose quantized mode to align clip endings with the global launch grid.

Instructions

Stop transport playback, and optionally every playing Session clip.

Returns:
    Dictionary reporting the transport stop and, where asked for, the clip stop.

Note:
    With ``quantized=True`` the clips stop on the next grid point rather than at
    once, so an immediate read can still show a clip playing without anything
    having gone wrong. Use play to resume playback, or set_arrangement_time(at_beat=0)
    to rewind the Arrangement timeline to the beginning.

    Stopping does not restore a parameter a clip envelope was driving. The envelope
    leaves the parameter at its last reached value and Live keeps no static baseline
    underneath to restore.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clipsNoTrue also stops every playing Session clip through song.stop_all_clips. False stops the transport only: the flag exists because that alone does not stop the Session clips.
quantizedNoTrue lets the clip stop fall on the global launch quantisation grid, so it can lag the call by up to a bar. False stops the clips immediately. Only read when clips is true.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / clips / description
      Added value: +"True also stops every playing Session clip through song.stop_all_clips. False stops the transport only: the flag exists because that alone does not stop the Session clips."
    • addedInput schema / properties / quantized / description
      Added value: +"True lets the clip stop fall on the global launch quantisation grid, so it can lag the call by up to a bar. False stops the clips immediately. Only read when clips is true."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses that quantized clip stops are grid-aligned and may not be reflected in an immediate read, and it warns that stopping does not restore envelope-driven parameters. These are non-obvious side effects an agent needs before invoking or interpreting the result.

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 description front-loads the main action, then uses compact Returns/Note sections; the envelope and timing caveats earn their place. It could be slightly tighter, but it is well structured and not padded.

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

Completeness5/5

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

For a 2-parameter tool with rich schema descriptions and annotations, the description covers the return value, timing semantics, side effects, and follow-up alternatives. Given an output schema exists, no critical behavioral information appears missing.

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?

The schema already fully documents both clips and quantized, including lag behavior, so the description doesn't add much parameter-level detail. The note about an immediate read still showing playback is a useful consequence but not a substantive expansion 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 opens with a specific verb and resource: 'Stop transport playback, and optionally every playing Session clip.' This immediately distinguishes it from siblings like play and set_arrangement_time, and the optional clip behavior frames its scope.

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?

It names relevant alternatives in context: 'Use play to resume playback, or set_arrangement_time(at_beat=0) to rewind the Arrangement timeline to the beginning.' This gives an agent clear follow-up actions, though it doesn't explicitly state when not to use stop.

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