Plan or stop Ableton Live playback immediately with a guarded, confirm-to-execute operation.
Plan or stop Live playback immediately using the guarded panic operation.
| Name | Required | Description | Default |
|---|---|---|---|
| dryRun | No | False executes with token and hash. | |
| planHash | No | Plan hash. | |
| confirmationToken | No | Single-use plan token. | |
| expectedStateVersion | Yes | Observed stateVersion. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.1Output schema / additionalPropertiesRemoved value: -trueOutput schema / anyOfAdded value: +[
+ {
+ "oneOf": [
+ {
+ "properties": {
+ "confirmation": {
+ "properties": {
+ "expiresAt": {
+ "type": "number"
+ },
+ "planHash": {
+ "pattern": "^[a-f0-9]{64}$",
+ "type": "string"
+ },
+ "token": {
+ "minLength": 1,
+ "type": "string"
+ }
+ },
+ "required": [
+ "token",
+ "planHash",
+ "expiresAt"
+ ],
+ "type": "object"
+ },
+ "dryRun": {
+ "const": true
+ },
+ "plan": {
+ "type": "object"
+ }
+ },
+ "required": [
+ "dryRun",
+ "plan",
+ "confirmation"
+ ],
+ "type": "object"
+ },
+ {
+ "properties": {
+ "dryRun": {
+ "const": false
+ },
+ "operationOutcome": {
+ "properties": {
+ "evidence": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "reason": {
+ "type": "string"
+ },
+ "schemaVersion": {
+ "const": 1
+ },
+ "status": {
+ "enum": [
+ "applied",
+ "outcome_unknown",
+ "postconditions_failed",
+ "pending_postconditions",
+ "pending_user_action"
+ ]
+ }
+ },
+ "required": [
+ "schemaVersion",
+ "status",
+ "reason",
+ "evidence"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "dryRun",
+ "operationOutcome"
+ ],
+ "type": "object"
+ }
+ ],
+ "properties": {
+ "dryRun": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "dryRun"
+ ],
+ "type": "object"
+ },
+ {
+ "properties": {
+ "error": {
+ "properties": {
+ "message": {
+ "type": "string"
+ },
+ "outcome": {
+ "enum": [
+ "unknown",
+ "not_executed"
+ ]
+ }
+ },
+ "required": [
+ "message",
+ "outcome"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "error"
+ ],
+ "type": "object"
+ }
+]v0.3.0Input schema / properties / confirmationToken / descriptionPrevious value: -"Short-lived, single-use token returned by the matching dry run."New value: +"Single-use plan token."Input schema / properties / dryRun / descriptionPrevious value: -"Omit or true to return a plan; false requires a valid confirmationToken."New value: +"False executes with token and hash."Input schema / properties / expectedStateVersion / descriptionPrevious value: -"Exact stateVersion observed immediately before planning."New value: +"Observed stateVersion."Input schema / properties / planHash / descriptionPrevious value: -"Hash returned by the matching dry run."New value: +"Plan hash."Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "type": "object"
+}v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=false, so the agent knows this mutates. The description adds the notions of 'guarded' and 'immediately', but it never explains the two-phase plan-then-execute protocol or that execution requires a plan hash plus single-use token, which is the behaviorally important part of this tool.
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 no padding or filler. It is efficient, though the compressed phrasing 'Plan or stop' sacrifices clarity for brevity.
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?
An output schema and full annotation set reduce the burden, but for a destructive operation with a multi-step confirmation workflow the description should at least state that a plan must be generated before execution and what stopping playback affects. It is minimally adequate rather than complete.
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 description coverage is 100%, so dryRun, planHash, confirmationToken, and expectedStateVersion are each documented in the schema. The description adds nothing about parameter semantics, which is acceptable at full coverage but earns only the baseline.
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?
The verb phrase 'Plan or stop Live playback immediately' identifies the resource (Live playback) and a stop action, but 'Plan or stop' conflates two distinct phases and is ambiguous on first read. It also fails to distinguish this from obvious siblings like transport_stop or stop_all_clips, which an agent would reasonably consider equivalent.
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 or when-not-to-use guidance is given, and no alternative is named even though transport_stop, stop_all_clips, and set_transport_context all overlap with stopping playback. The word 'guarded' hints that this is not the ordinary stop path, but the agent is left to infer that.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.