Skip to main content
Glama
Sign In
ableton-mcp

ableton-mcp

by mrinalghosh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

stop_clip

Stop a specific clip on a given track in Ableton Live. Provide track and clip numbers to halt playback.

Instructions

Stop a clip.

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": "<track>",
      "clip": "<clip>"
    },
    "name": "stop_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYes
clipYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states 'Stop a clip' but does not explain what happens if the clip is not playing, if it affects other clips, or if there are any side effects (e.g., resetting position).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While extremely concise, the description is under-specified and fails to provide essential context. Conciseness should not come at the expense of clarity or completeness.

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

Completeness1/5

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

Given no annotations, no output schema, and only 2 parameters, the description should at minimum explain the parameters and return value. It provides none of this, making it insufficient for reliable tool selection and invocation.

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?

The input schema has 2 parameters (track, clip) with 0% description coverage. The description adds no meaning beyond the schema, leaving the agent to guess what integer values represent (e.g., track index, clip index).

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?

The description clearly states the action (stop) and the resource (a clip). It is a specific verb+resource combination, but it does not distinguish between different types of clips (e.g., audio vs. MIDI) or contrast with sibling tools like fire_clip.

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?

No guidance is provided on when to use this tool vs. alternatives like fire_clip, or what prerequisites are needed (e.g., the clip must be playing). The agent receives no context for appropriate invocation.

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