Skip to main content
Glama

undo

Revert or reapply one Live change step, including a batch, similar to Cmd+Z. Because Live's history is shared, read the state afterward to see what changed.

Instructions

Undo or redo one step in Live, like Cmd+Z. Every Tonable change is one step (a batch too). Live's undo history is shared with everyone working in the Set, so read the state afterwards to see what changed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "undo"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoundo (Cmd+Z) or redo (Shift+Cmd+Z).undo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior4/5

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

Beyond annotations it discloses the crucial non-obvious trait that undo history is shared across everyone in the Set, meaning the caller may revert another collaborator's work, and it recommends reading state afterward. Annotations only cover the read-only/destructive/idempotent profile, so this multi-user context is real added value. It stops short of describing error behavior when the history is empty or whether a step is scoped to the calling client.

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 sentences, front-loaded with the core action and analogy, followed by the one caveat that matters. No filler and nothing needing re-reading.

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

Completeness4/5

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

For a one-parameter mutation with no output schema, the description covers granularity, the shared-history caveat, and the recommended verification step. Minor gaps remain around behavior on empty history and whether the step is per-client or per-Set, but the essentials for correct invocation are present.

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

Parameters3/5

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

Schema coverage is 100% and the single enum parameter already documents 'undo (Cmd+Z) or redo (Shift+Cmd+Z)'. The description reinforces the semantics with the same analogy but adds nothing the schema does not already state, so the baseline 3 applies.

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 states a specific verb and scope: 'Undo or redo one step in Live, like Cmd+Z.' The Cmd+Z analogy plus the note that 'every Tonable change is one step (a batch too)' pins down the granularity exactly, and no sibling tool competes for this 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?

It gives clear usage context — call this to step backward or forward through changes — and adds an operational follow-up ('read the state afterwards to see what changed'). It does not name an alternative tool or state when not to use it, but no sibling overlaps with undo/redo, so the gap is small.

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