Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

undo

Reverses the last edit on the active sprite in the live Aseprite editor, restoring the previous state so you can quickly correct unwanted changes.

Instructions

Undo the last edit on the active sprite (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": "undo"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior2/5

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

Annotations carry only a title, so the description must disclose behavior itself. It does not say whether undo is repeatable, what happens when the undo stack is empty, whether it is destructive/persistent, or whether it requires a live session token — significant gaps for a mutation tool with no hints.

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. It is efficient, though the brevity trades away information the agent needs about the file parameter.

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 conceptually simple undo action, the description covers the core action and the live-editor constraint. It is not complete for an agent that must decide what the 'file' argument does or how to handle an empty history, and no output schema exists to fill that in.

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?

There is one optional 'file' parameter with 0% schema description coverage, and the description never mentions it. It is unclear whether 'file' targets a specific sprite document, overrides the 'active sprite', or is ignored in live edit mode, so the description does not compensate for the schema gap.

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 names a specific verb (undo) and the exact target (the last edit on the active sprite), so the resource is unambiguous. It does not distinguish itself from a possible redo or from history-related siblings, but the purpose itself is crisp.

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 '(live editor)' qualifier implies the tool applies only to an active editing session, which is genuine usage context. It stops short of saying what to do when there is no history or which alternative to use instead, so guidance is only implied.

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