Skip to main content
Glama
Sign In
AbletonMCP

AbletonMCP

by rephlex187
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

undo

Reverse the most recent change in your Ableton Live session to restore a previous state.

Instructions

Undo the last action in Ableton Live.

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": {
      "ctx": "<ctx>"
    },
    "name": "undo"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctxYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.4/5.0
Behavior1/5

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

No annotations are present, and the description fails to disclose essential behaviors such as whether multiple undo steps are supported, what happens if no action exists, or any side effects.

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

Conciseness3/5

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

The description is a single sentence, which is front-loaded, but it is too brief to be maximally helpful; some additional detail would improve clarity without losing conciseness.

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 the lack of output schema and the simplicity of the tool, the description omits critical context such as the relationship with 'can_undo' and redo, and does not explain the required context parameter.

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 only parameter 'ctx' is an internal Context object with no tool-specific description, and schema coverage is 0% (the description does not compensate for missing parameter guidance).

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 description clearly states the verb ('Undo') and resource ('last action in Ableton Live'), and distinguishes well from siblings like 'redo' and 'can_undo'.

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 versus alternatives like 'can_undo' or 'redo', nor any prerequisites or usage context.

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