aseprite-mcp

Overview Schema Source Related Servers Discussions Admin

copy_cel

Copy a cel's image to another layer or frame, optionally into another open sprite, to reuse artwork across animations without redrawing it.

Instructions

Copies a cel's image to another layer/frame (and optionally another open sprite).

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": "copy_cel"
  }
}

Input Schema

Name	Required	Description
`x`	No
`y`	No
`save`	No	Batch mode: write changes back to the sprite file (default true)
`sprite`	No	Destination sprite
`backend`	No	auto (default): live Aseprite if connected, else headless batch
`toFrame`	No
`toLayer`	No
`fromFrame`	No	1-based frame number. Defaults to the active frame (or 1).
`fromLayer`	No	Layer name, 'Group/Child' path, or 1-based index from get_sprite_info. Defaults to the active layer.
`fromSprite`	No	Source sprite (default: same)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 18, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations declare this is a write operation (readOnlyHint=false) that is non-destructive, so safety is partly covered. The description adds that the copy can target a different sprite, but does not disclose whether an existing destination cel is overwritten (potential content loss), nor the live-vs-batch backend implications. Some added context, but a key mutation consequence is left implicit.

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 well-formed sentence with the operation front-loaded and the optional extension parenthetically scoped. No wasted words, though it is quite terse for a 10-parameter mutation tool.

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 10-parameter mutation with no output schema and minimal annotations, the description omits the meaning of the x/y parameters and the overwrite/return behavior. Annotations carry the safety profile, which lowers the bar, but the description leaves gaps an agent would need to close by opening the schema.

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 10 parameters and only 60% schema description coverage, the description's mention of 'another layer/frame' and 'another open sprite' loosely maps to toLayer/toFrame/sprite, but adds no syntax or format detail. The x, y coordinates go entirely unaddressed in both the description and (by coverage gap) parts of the schema, so it only marginally compensates.

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?

States a specific verb (Copies) and resource (a cel's image) with the destination scope (another layer/frame, optionally another sprite). It distinguishes the operation from sibling tools like link_cels (which links rather than copies) and duplicate_layer (which duplicates whole layers). It stops short of explicitly naming a sibling, but the function is unambiguous.

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?

The description implies when it applies (moving a cel's image to a target) but offers no explicit when-to-use vs alternatives, no prerequisites, and no note about how it differs from link_cels or get_cels/update_cel workflows. Nothing routes the agent among the copy-adjacent siblings.

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

Deploy Server