Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

reverse_frames

Reverses sprite frame order, including cels on every layer and durations, for the whole sprite or an inclusive frame range as one undoable edit.

Instructions

Reverse frame order (cels on every layer, plus durations) — the whole sprite by default, or the inclusive [from_frame..to_frame] range. One undo step.

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": "reverse_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
to_frameNo
from_frameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations carry only a title, so the description bears the full disclosure burden, and it delivers the two facts that matter most for a mutation: durations are reversed along with the cels on every layer, and the entire operation collapses into 'One undo step.' It does not state whether frame count changes, what happens with an out-of-range or inverted from/to pair, or what the response contains.

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?

A single front-loaded sentence with a parenthetical clarifying the payload, followed by the scope default and the undo guarantee. No filler, and the most important constraint (what gets reversed) comes first.

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 three-parameter mutation with no output schema and no behavioral annotations, the description covers the essential semantics: affected data, scope, and undo behavior. Minor omissions — treatment of invalid ranges and the file parameter — are the only remaining gaps.

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

Parameters4/5

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

Schema coverage is 0%, so the description must supply meaning, and it does for the two scoping parameters: the range is explicitly inclusive and omitting it reverses the whole sprite. The file parameter is never mentioned, leaving the agent to infer that null means the current sprite.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (reverse frame order) and immediately qualifies what is affected: 'cels on every layer, plus durations.' That detail separates it from neighboring frame tools like add_frames or tween_frames, which modify frame content rather than reordering existing frames.

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 description gives scoping guidance — whole sprite by default, or the inclusive [from_frame..to_frame] range — which tells the agent how to invoke it in two modes. It does not say when to prefer this over a related operation (e.g., versus undo for restoring a prior state) or note any preconditions such as an existing animation with at least two frames.

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