Skip to main content
Glama
Sign In
Aseprite MCP Tools

Aseprite MCP Tools

by NosytLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

tween_cel_positions_eased

Interpolate cel positions across a frame range using customizable easing functions for smooth animation transitions.

Instructions

Tween cel positions with easing across a frame range.

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": {
      "filename": "<filename>",
      "layer_name": "<layer_name>",
      "start_frame": "<start_frame>",
      "end_frame": "<end_frame>",
      "start_x": "<start_x>",
      "start_y": "<start_y>",
      "end_x": "<end_x>",
      "end_y": "<end_y>"
    },
    "name": "tween_cel_positions_eased"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_xYes
end_yYes
easingNosmoothstep
start_xYes
start_yYes
filenameYes
end_frameYes
layer_nameYes
start_frameYes
source_frame_indexNo
create_missing_celsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior, but it only states basic purpose. It omits details like what happens to existing cels, coordinate system, or prerequisite state.

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 sentence with no wasted words. However, it could include more helpful information without becoming verbose.

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?

With 11 parameters and no output schema, the description is far from complete. Key parameters like 'source_frame_index' and 'create_missing_cels' are unexplained, making the tool hard to use correctly.

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% and the description adds no parameter details. While parameter names like start_x are somewhat self-explanatory, values like 'easing' type and 'source_frame_index' lack clarity.

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?

The description 'Tween cel positions with easing across a frame range' clearly states it tweens cel positions with easing, distinguishing it from the sibling 'tween_cel_positions' which likely lacks easing.

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?

No explicit usage guidelines are provided. The description implies it should be used for animating cel positions with easing, but does not discuss alternatives or when not to use it.

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