Skip to main content
Glama
pixelorama-mcp
by Aeroscoop

redo

Restore previously undone steps in the active Pixelorama project, up to a specified number, and return the names of the restored steps.

Instructions

Redo the last n undone steps in the active project, like Ctrl+Y. Returns the names of the steps redone.

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
stepsNoNumber of steps, default 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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; it does disclose the mutation of project state and even the return value (names of steps redone), which is helpful since no output schema exists. However, it does not say what happens when n exceeds available redo history (error vs. clamp to zero), nor whether redo history is cleared by new actions.

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 sentences, front-loaded with the core action and scope, followed by the return value. Every sentence earns its place and nothing is redundant.

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 simple one-optional-parameter tool with no annotations or output schema, the description covers action, scope, analogy, and return value — enough to call it correctly. The only shortfall is edge-case behavior at the boundaries of redo history.

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

Parameters5/5

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

Schema description coverage is 100% already (the steps parameter documents 'Number of steps, default 1' with min 1 / max 50). The description reinforces this by framing it as 'the last n undone steps', matching the parameter's intent exactly with no ambiguity.

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 resource (the last n undone steps in the active project), plus a Ctrl+Y analogy that makes the semantics immediately legible and implicitly contrasts with the undo sibling. It does not name the undo sibling explicitly, so sibling differentiation is inferred rather than stated, keeping it from a 5.

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?

Usage is implied by 'undone steps' — an agent can infer this applies after one or more undo operations in the active project — but there is no explicit when-to-use statement, no mention of the undo alternative, and no precondition such as requiring a selected/active project.

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