Skip to main content
Glama
diivi
by diivi

offset_cel_positions

Offset cel positions by a delta across a frame range. Adjust layer cels by specifying horizontal and vertical pixel offsets for a range of frames.

Instructions

Offset cel positions by a delta across a frame range.

Args: filename: Name of the Aseprite file to modify layer_name: Layer name to target start_frame: Starting frame index (1-based) end_frame: Ending frame index (1-based, inclusive) dx: X delta in pixels dy: Y delta in pixels

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
layer_nameYes
start_frameYes
end_frameYes
dxYes
dyYes
Behavior2/5

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

No annotations exist, so the description must fully convey behavior. It describes the operation as offsetting positions but does not clarify whether it modifies existing keyframes, adds keyframes, or handles missing cels. Basic transparency is present, but key behavioral details are missing.

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?

The description is concise: one sentence for purpose followed by a list of parameters with short, clear descriptions. No unnecessary words or repetition.

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?

Given the lack of output schema and 6 required parameters, the description covers the basic operation and parameter meanings. However, it omits details on return value, error conditions, and whether the offset applies to all cels in the range or just keyframes. Adequate but not comprehensive.

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 descriptions are absent (0% coverage), so the description's parameter explanations carry the burden. Each parameter gets a brief, clarifying description: e.g., 'Starting frame index (1-based)' and 'Name of the Aseprite file to modify'. This adds meaningful context beyond schema titles.

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 clearly states 'Offset cel positions by a delta across a frame range,' a specific verb and resource. This distinguishes it from similar tools like 'set_cel_position' (single frame) and 'tween_cel_positions' (animation).

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?

No guidance on when to use this tool versus alternatives like 'set_cel_position' or 'tween_cel_positions'. No prerequisites or caveats are mentioned, leaving the agent to infer context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/diivi/aseprite-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server