Stops playback of a running clip slot in Ableton Live 12 using track and slot indices, so you can halt individual clips without stopping the entire session.
Stops playback of a running clip slot in Ableton Live 12 (Clip.stop).
| Name | Required | Description | Default |
|---|---|---|---|
| slot_index | Yes | Zero-based clip slot index. | |
| track_index | Yes | Zero-based track index. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It states the action but not idempotency, error behavior for a non-playing slot, side effects, or what the call returns, so an agent cannot anticipate failure modes.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with zero waste, and the LOM reference adds a little grounding value. Appropriately sized for a trivial two-parameter action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple stop action with no output schema, the description is minimally sufficient. It omits failure behavior and the relationship to transport-level stop, which would matter to an agent choosing between the two.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with both track_index and slot_index documented as zero-based indices. The description adds nothing beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Stops') and resource ('playback of a running clip slot'), plus the underlying LOM call (Clip.stop) for grounding. It doesn't explicitly differentiate from sibling live12_transport_stop or live12_clip_fire, leaving the agent to infer that this targets one slot rather than global transport.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use/when-not guidance. The phrase 'running clip slot' hints at a precondition, but it never says what to do if the slot isn't playing, nor routes the agent between this and live12_transport_stop or live12_clip_fire.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.