Skip to main content
Glama

redo

Restore actions removed by undo, up to 50 steps, only if no other changes occurred since. Recover edits in Ableton Live after an accidental undo.

Instructions

Redo what undo just took back (as long as nothing else changed since).

Parameters:

  • steps: How many steps to redo (1–50)

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": "redo"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one meaningful behavioral trait: redo is only valid while the history state is unchanged since the undo. It says nothing about what happens on failure (error vs. silent no-op), whether redo history is truncated after a new edit, or whether the operation is reversible.

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 short blocks: a one-line behavioral statement followed by a bulleted parameter note. Everything is front-loaded and no sentence is redundant.

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?

The tool is simple and an output schema exists, so return values need no explanation. However, for a history-mutating operation with zero annotation coverage, the definition should mention failure/edge behavior (e.g., no redo stack available, exceeding 50 steps), which is currently absent.

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

Parameters4/5

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

Schema coverage is 0% – the only parameter is documented as an integer with default 1 but no title-level detail beyond 'Steps'. The description compensates by explaining the parameter's meaning and adding a hard bound of 1–50 that appears nowhere in the schema, which is exactly the value the description should supply.

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 pairs a specific verb with its resource: 'Redo what undo just took back' leaves no doubt about the operation. It implicitly distinguishes itself from the sibling 'undo' by defining itself relative to it, though it never names other reverting/replaying alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical 'as long as nothing else changed since' gives a real precondition for when this tool will apply, which is genuine usage guidance. It does not say what to do when that precondition fails (fall back to undo? re-execute?) or name alternatives, so usage is implied rather than fully spelled out.

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