Skip to main content
Glama

redo

Reapply a specified number of previously undone actions in DaVinci Resolve to restore edits after an undo.

Instructions

Redo N actions (Cmd+Shift+Z) in Resolve.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries full disclosure burden. It reveals only that the operation mirrors Cmd+Shift+Z; it does not state whether the redo history is per-project, whether an empty stack errors or is a no-op, or whether the change is reversible (undoable).

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

Conciseness4/5

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

A single compact sentence with the shortcut hint front-loaded alongside the action. Nothing is wasted, though the terseness leaves the definition thin.

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?

For a one-optional-parameter tool with no output schema, the description covers the core operation. It is still missing edge-case and state behavior (empty history, scope of the redo stack) that an agent would want before calling.

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 0% and the only parameter is titled 'Steps' with default 1. The phrase 'N actions' partially clarifies that 'steps' means the number of redo operations to apply, which is modest but real added meaning beyond the bare schema.

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?

States a specific verb (redo) and the count of actions, plus the desktop shortcut (Cmd+Shift+Z) that anchors the concept for an agent or user. It does not distinguish itself from an undo counterpart, but the verb+resource is unambiguous.

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 on when to use this vs. an undo-style action, no mention of what happens when the redo stack is empty, and no prerequisites. Usage is only implied by the shortcut reference.

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