Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

redo

Restore the last undone edit in a live or headless Aseprite canvas, optionally targeting a specific file, so pixel-art work can continue without losing changes.

Instructions

Redo the last undone edit (live editor).

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
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations supply only a title, so the description carries the full behavioral burden and does little with it. It does not say what happens when the redo stack is empty, whether the operation is scoped to a live session, or whether it mutates saved state. Only the '(live editor)' aside hints at the operating context.

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 front-loaded sentence with no filler; the action is stated first. It is terse to the point of under-specification, but no sentence is wasted.

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

Completeness2/5

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

For a trivially simple action this is close to sufficient, but two gaps matter: the optional 'file' parameter is unexplained, and the no-op/failure behavior with an empty redo stack is unknown. With no annotations and no output schema, the description should have covered these.

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

Parameters2/5

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

Schema description coverage is 0% for the single optional 'file' parameter, and the description never mentions it. An agent cannot tell from either source whether 'file' targets a specific document's redo stack or is merely an ignored/legacy argument.

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 states a specific verb and resource ('Redo the last undone edit') that an agent can immediately distinguish from an undo operation. The parenthetical '(live editor)' narrows the domain further. It stops short of naming a sibling alternative, but the action itself 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 Guidelines3/5

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

Usage is only implied: 'the last undone edit' suggests this applies after an undo, and '(live editor)' suggests it operates on the active editing session rather than a stored project. There is no explicit when-to-use, when-not-to-use, or guidance on what to do if there is no undone edit to redo.

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