Skip to main content
Glama
Sign In
aseprite-mcp

aseprite-mcp

by shin2344234
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_frames

Insert one or more frames into a sprite animation at a chosen position, copying existing cels or creating blank frames.

Instructions

Adds frames. By default copies the previous frame's cels; empty=true adds blank frames.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoFrame number for the first new frame (default: end)
saveNoBatch mode: write changes back to the sprite file (default true)
countNo
emptyNo
spriteNoFile path, open tab title, or sprite id. Defaults to the active sprite (live). Batch mode needs a file path.
backendNoauto (default): live Aseprite if connected, else headless batch
copyFromNoFrame to copy (default: the frame before 'at')
durationMsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, correctly signaling a non-destructive mutation. The description adds genuinely useful context beyond that: the default of copying the previous frame's cels and the empty=true override. It omits save/backend behavior, but that is documented in the schema.

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?

Two tight sentences, zero filler, with the primary action front-loaded and the key behavioral default immediately following.

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 mutation tool with annotations and no output schema, the description covers the core default behavior adequately but leaves the return value, batch-mode effects, and sibling routing unaddressed. It is minimally sufficient rather than complete.

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?

Schema coverage is 63%, with 'empty', 'count', and 'durationMs' lacking descriptions. The description compensates for 'empty' (blank vs copied frames) and hints at copyFrom's default, but says nothing about count or durationMs, so it only partially bridges the gap.

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?

'Adds frames' states a specific verb and resource, clearly distinguishing it from delete_frames and move_frame. The added clause about cel-copying behavior further sharpens what the operation does, though it never explicitly names a sibling to route against.

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 via the 'empty=true adds blank frames' distinction, which steers the agent toward the right option for blank vs cloned frames. However, it offers no explicit when-to-use guidance relative to copy_cel/link_cels or any prerequisites, leaving routing to inference.

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