Skip to main content
Glama
pixelorama-mcp
by Aeroscoop

undo

Revert the last one or more actions in the active Pixelorama project to correct mistakes, like Ctrl+Z, and return the names of the steps reverted.

Instructions

Undo the last n steps in the active project, like Ctrl+Z. Returns the names of the steps undone.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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: it does disclose that this is a reversible-style mutation bounded by a step count and that it returns the names of the undone steps, which is useful. It does not state what happens when n exceeds available history, whether the undo itself can be reverted via redo, or whether the count is clamped rather than erroring.

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 action and its scope, followed by the return value. Nothing is padded or 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 one-parameter utility operation, this covers the action, the bound, and the return value, which is essentially everything an agent needs to invoke it. Only the exhausted-history and redo-interaction behavior are left unstated, which is a minor omission for a tool this simple.

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 parameter already documents its range (1-50) and default of 1; the description's 'last n steps' echoes that without adding format or edge-case meaning. Baseline 3 applies when the schema does the heavy lifting.

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 ('Undo') and scope ('the last n steps in the active project'), plus a Ctrl+Z analogy that pins the semantics precisely. It never names the 'redo' sibling, but the inverse relationship is self-evident, so the only gap is the lack of explicit sibling differentiation.

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 phrase 'in the active project' implicitly signals the prerequisite that a project must be open, and Ctrl+Z implies 'use when you want to revert recent edits.' There is no explicit when-not guidance, no mention of redo as the counterpart for redressing an over-undo, and no note on what happens at the edge of history.

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