Skip to main content
Glama

stop

Idempotent

Halt transport playback in Ableton Live, with an option to also halt every playing Session clip. Quantized timing aligns clip halts to the global launch grid for precise live control.

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(time=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. Dates show when Glama detected each change.

  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.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the quantized stop timing (clips may lag up to the next grid point), the fact that an immediate read may still show a clip playing, and the envelope side effect that stopping does not restore a parameter to a baseline. These are non-obvious behavioral traits that an agent needs to interpret results correctly, and they do not contradict the annotations.

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?

The description is compact and well-structured: one opening sentence, a short Returns note, and a focused behavioral note. Each paragraph earns its place; the envelope side effect is not padding and the usage alternatives are integrated naturally.

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?

Given the rich input schema for both parameters and the presence of an output schema, the description covers all essential behavioral context: stop scope, quantized timing, return value, resume/rewind alternatives, and the envelope side effect. Nothing an agent needs to invoke the tool correctly is missing.

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?

The schema already describes both boolean parameters thoroughly (100% coverage), so the baseline is adequate. The description adds value by explaining the quantized=True behavior in terms of grid timing and the implication for immediate reads, complementing rather than repeating the schema exactly. The clips parameter is only summarized, but the schema carries its detail.

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 opening sentence states a specific verb and resource: 'Stop transport playback, and optionally every playing Session clip.' It clearly distinguishes the action from siblings like play and set_arrangement_time by naming those tools for resume/rewind in the note, so an agent can tell what this tool does.

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?

The description gives clear context for stopping playback and explains that play should be used to resume and set_arrangement_time(time=0) to rewind. It does not spell out explicit when-not-to-use conditions, but the alternative routing is present and sufficient for this tool.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/romanstark/live-maestro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server