Skip to main content
Glama
Sign In
Aseprite Asset MCP

Aseprite Asset MCP

by jdsalasca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

offset_cel_positions

Move cel positions on a layer across a frame range by dx and dy offsets to reposition animation frames in an Aseprite asset.

Instructions

Offset cel positions 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>",
      "dx": "<dx>",
      "dy": "<dy>"
    },
    "name": "offset_cel_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
dxYes
dyYes
filenameYes
end_frameYes
layer_nameYes
start_frameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Offset' implies a mutating operation, but it does not state whether it modifies existing cel positions, whether offsets are additive, whether it affects all cels in the range, whether it is reversible, or what the result looks like.

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 description is a single tight sentence with no filler, front-loading the verb and resource. It is concise, though arguably too sparse for a six-parameter mutating tool.

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 mutating tool with no annotations, no output schema, six required parameters, and no sibling differentiation, the description is materially incomplete. An agent would not know the precise effect, prerequisites, or how to select this over related cel-position tools.

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%, so the description must compensate, but it only loosely maps 'offset' to dx/dy and 'frame range' to start_frame/end_frame. It does not clarify units, coordinate space, the role of filename/layer_name, or how dx/dy apply to existing positions.

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 uses a specific verb ('Offset') and a clear resource ('cel positions') with an explicit scope ('across a frame range'). It is understandable on its own, but it does not differentiate itself from siblings like set_cel_position or tween_cel_positions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus siblings such as set_cel_position, tween_cel_positions, or propagate_cels. The scope 'across a frame range' hints at batch use, but no explicit usage context, exclusions, or alternatives are provided.

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