Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

tween_frames

Insert in-between frames that slide a start frame's art toward the end frame's position, handling moved cels and redrawn art. Choose linear, ease_in, ease_out, or smoothstep easing.

Instructions

Insert count in-between frames between from_frame and to_frame that slide the start frame's art toward where the end frame's art sits, so it works for moved cels and for art redrawn in a new place. It moves the art without reshaping it, and refuses if the art hasn't moved. easing: linear, ease_in, ease_out, or smoothstep. Check the result with look_animation. Headless: pass file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from_frame": "<from_frame>",
      "to_frame": "<to_frame>"
    },
    "name": "tween_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
countNo
layerNo
easingNolinear
to_frameYes
from_frameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

With only a title annotation, the description carries real behavioral weight: it discloses that it translates art rather than reshaping it, that it fails when the art is unchanged, that easing accepts four named curves, and that headless operation requires file. That is meaningful disclosure for a mutation tool. It omits what happens to frames after to_frame, whether the response reports anything, and any permission or scope constraints.

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?

The core verb-and-resource statement is front-loaded, followed by the key behavioral constraint, the easing vocabulary, and the verification pointer. Every sentence earns its place, though the RST double-backtick markup adds noise and the easing detail interrupts the behavioral narrative mid-paragraph.

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 mutation tool with no annotations and no output schema, the description covers purpose, precondition for failure, easing values, headless requirement, and a suggested verification path via look_animation. The remaining gaps are the undocumented layer parameter and the absence of any statement about what happens to downstream frames or what the call returns.

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 coverage is 0%, yet the description explains nearly all six parameters: count as the number of in-betweens, from_frame and to_frame as the bracketing frames, easing with its four allowed values (information the schema entirely lacks, since it declares no enum), and file as the headless-mode requirement. Only layer is left unexplained, a minor gap against otherwise strong compensation.

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: it inserts in-between frames between from_frame and to_frame that slide the start art toward the end art's position. The phrase 'works for moved cels and for art redrawn in a new place' makes the resulting behavior concrete, and 'moves the art without reshaping it' distinguishes it from a redraw. It stops short of naming a sibling such as add_frames, so it doesn't fully differentiate itself from the family of frame-insertion tools.

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?

Guidance is implied rather than explicit: the tool refuses when the art hasn't moved, which tells an agent the precondition for calling it, and 'Check the result with look_animation' gives a verification workflow. 'Headless: pass file' indicates the environment condition for the file parameter. However, there is no statement of when to prefer this over add_frames or reverse_frames, and no when-not-to-use guidance beyond the refusal case.

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