Skip to main content
Glama
with-pebbly

aseprite-ai-artist

by with-pebbly

Frames

frame
Destructive

Manage animation steps in Aseprite: list, add, duplicate, delete, reorder, activate, or set durations. Adjust per-step timing to shape cycle motion.

Instructions

Manage animation frames. Ops: 'list', 'add', 'duplicate', 'delete', 'set_duration', 'activate', 'reorder'. Durations are milliseconds per frame and carry most of the life in a cycle — hold a contact pose longer than a pass pose. Use count to add several at once and durations to set a whole cycle's timing in one call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opYes
countNo
frameNo1-based frame number. Omit to use the active frame.
spriteNoSprite filename or id. Omit to use the sprite Aseprite has focused.
toIndexNoFor 'reorder'.
linkCelsNoFor 'duplicate': share the cel image instead of copying it, so edits apply to both.
durationsNoPer-frame durations from frame 1, for 'set_duration'.
afterFrameNoInsert position. Default: at the end.
durationMsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
framesNo
spriteYes
frameCountYes
activeFrameNo
totalDurationMsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already indicate destructive behavior, and the description adds useful context about durations being milliseconds and about using count for bulk addition. However, it does not disclose side effects such as index shifting after deletion or reorder behavior, relying partially on the destructive hint.

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 compact and front-loaded with the main purpose. The extra guidance on durations and count is useful and earns its place, though the contact-pose analogy is slightly stylistic rather than essential.

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?

For a multi-operation tool with nine parameters, the description gives useful tips but does not map operations to their relevant parameters. An agent may still need to infer which parameters apply to each op, though the schema and output schema help fill some gaps.

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

Parameters3/5

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

With 67% schema coverage, the description adds meaning for count and durations, which are otherwise under-documented. It does not fully compensate for all undocumented parameters like durationMs, but it provides valuable context for the most nuanced timing-related parameters.

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 clearly identifies the tool as managing animation frames and lists the supported operations. It is specific enough to distinguish from siblings like layer or cel, but it does not explicitly differentiate itself from those sibling 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?

The description implies usage for frame-related operations and offers practical tips for count and durations. However, it does not explicitly state when to prefer this tool over siblings, nor does it provide exclusions or conditions for 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.

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/with-pebbly/aseprite-ai-artist'

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