Skip to main content
Glama
Sign In
Aseprite MCP Tools

Aseprite MCP Tools

by ZeroTian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

propagate_cels

Copy cels from one frame to multiple frames for selected layers in an Aseprite file, optionally overwriting existing cels.

Instructions

Copy cels from a source frame to a range of frames for specific layers.

Args: filename: Name of the Aseprite file to modify layer_names: List of layer names to copy source_frame: Frame index to copy from (1-based) start_frame: Start frame index (1-based) end_frame: End frame index (1-based, inclusive) replace: Whether to overwrite existing cels (default: True)

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_names": "<layer_names>",
      "source_frame": "<source_frame>",
      "start_frame": "<start_frame>",
      "end_frame": "<end_frame>"
    },
    "name": "propagate_cels"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
layer_namesYes
source_frameYes
start_frameYes
end_frameYes
replaceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided. The description does not disclose critical behaviors such as whether source cels are deleted, behavior when replace=False (merge?), or permission requirements. Only notes 'replace: Whether to overwrite existing cels' but doesn't explain the alternative.

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 one-line summary and parameter list are concise with no redundant text. The parameter list is slightly lengthy but organized. No wasted sentences; earns its place.

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 6 parameters, no output schema, and no annotations, the description covers basic usage but omits behavioral context (e.g., what if source_frame equals a target frame? Does it error on nonexistent layers?). Adequate but not complete.

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 description coverage is 0%, so the description carries the burden. It provides clear 1-based indexing for frames, lists layer_names as a list, and explains the replace parameter. However, it lacks details like allowed values for layer_names or what happens when replace=False.

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 states 'Copy cels from a source frame to a range of frames for specific layers,' which is a specific verb (copy) and resource (cels across frames for layers). It clearly distinguishes from sibling tools like copy_cel (single cel) and propagate_frame_to_range (copies frames not cels).

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 explicit when-to-use or alternatives guidance. The description only lists parameters, failing to differentiate from tools like copy_cel or propagate_frame_to_range. No context on when to use replace=True/False.

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