Skip to main content
Glama
Sign In
Aseprite Asset MCP

Aseprite Asset MCP

by jdsalasca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

copy_cel

Copy a layer cel from one frame to another in an Aseprite file, replacing the destination cel by default.

Instructions

Copy one layer cel to another frame, replacing the destination by default.

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>",
      "source_frame": "<source_frame>",
      "target_frame": "<target_frame>"
    },
    "name": "copy_cel"
  }
}

Input Schema

NameRequiredDescriptionDefault
replaceNo
filenameYes
layer_nameYes
source_frameYes
target_frameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose that the destination is replaced 'by default'. However, it does not explain what happens when replace=false, whether source content is preserved, or what the function returns. This is partial transparency for a potentially destructive operation.

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 efficient sentence, front-loaded with the action and target. The default replacement behavior adds meaningful detail without padding. Slightly more explicit parameter mapping would improve it, but it earns its place.

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?

Given no annotations and no output schema, the description is too thin for a 5-parameter mutation tool. It lacks details on the replace parameter's semantics, failure conditions, prerequisites (e.g., layer existence), and the behavior when the destination cel contains content. An agent could misuse this tool without more context.

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 description coverage is 0%, so the description must compensate for meaning. It clarifies the domain ('layer cel') and the default replace behavior, and implicitly maps source_frame/target_frame. Yet it does not explicitly explain the replace parameter's effect or frame indexing conventions, leaving gaps.

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 states a specific verb ('copy') and resource ('one layer cel') with a clear source and destination ('to another frame'), and it adds the default replacement behavior. It does not explicitly name sibling tools like copy_frame or copy_sprite, but the layer-cel specificity gives it enough distinctiveness.

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 is given about when to use this tool versus alternatives such as copy_frame, copy_sprite, or propagate_cels. There are no conditions, prerequisites, or exclusions provided, leaving the agent to infer the use case.

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