ableton-mind

Overview Schema Source Related Servers Discussions Admin

clip_stop

Stop playback of a specific clip slot in Ableton Live without affecting global transport. Returns unchanged status if clip is already stopped.

Instructions

Stop playback for a specific session clip slot. Use to halt one clip without stopping the global transport. Idempotent for already-stopped clips; returns changed=false when no launch state changed and marks async playback verification unverified.

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_slot_index": "<clip_slot_index>"
    },
    "name": "clip_stop"
  }
}

Input Schema

Name	Required	Description	Default
`track_index`	Yes
`clip_slot_index`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Discloses idempotence and return behavior (changed=false, async marking). No annotations exist, so description carries burden; could mention prerequisites like transport state.

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 efficient sentences with no redundancy. Front-loaded with core action and purpose.

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?

Covers usage and behavior, but missing parameter explanations for a tool with two required inputs. Acceptable but not fully informative.

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

Parameters1/5

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

Schema coverage 0% and description does not explain track_index or clip_slot_index parameters. No additional meaning beyond 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?

Explicit verb 'stop' and resource 'clip slot', distinguishes from global transport stop. Also mentions idempotency and return behavior.

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?

States when to use: 'halt one clip without stopping the global transport'. Lacks explicit alternatives, but sibling tools like 'stop' and 'clip_fire' provide context.

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