Skip to main content
Glama
baichuan4167-lang

aseprite-mcp

by baichuan4167-lang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

aseprite_duplicate_frame

Copies a frame with all its layers to the next slot, letting you build animations by editing only changed parts instead of redrawing every frame.

Instructions

Copy a frame (all layers) to the next slot. The fastest way to build an animation: duplicate, then move or redraw only the parts that change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYesZero-based frame index (omit for the first frame).
documentNoDocument to act on: a short name inside the art folder ("hero"), a relative path, or an absolute .aseprite path. Omit to use the active document.
durationMsNoDuration for the copy in ms.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses that all layers are copied to the next slot, but omits side effects such as whether subsequent frames shift, undo behavior, and return information.

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 front-loaded sentences with no wasted words. The second sentence earns its place by giving a concrete animation-building rationale.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given low complexity, full schema coverage, and no output schema, the description supplies enough purpose and usage context to invoke correctly. It could mention side effects, but that is a minor gap for this simple frame-duplication operation.

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 100%, so the index, document, and duration parameters are already documented. The description adds only the scoping phrase 'all layers' and target phrase 'next slot', not parameter syntax or defaults.

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?

States a specific verb (Copy) and resource (frame), plus explicit scope (all layers) and target (next slot). This differentiates it operationally from siblings like move_frame and copy_cel even without naming them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a clear usage context: the fastest way to build an animation by duplicating and then editing only changed parts. It does not explicitly list alternatives or when-not-to-use conditions.

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