Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

duplicate_layer

Copies a layer and all its cels, placing the duplicate directly above the original in the sprite—useful for creating variations or backups without rebuilding artwork.

Instructions

Duplicate a layer (with its cels) above the original.

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": {
      "name": "<name>"
    },
    "name": "duplicate_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior3/5

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

With only a title annotation and no readOnly/destructive hints, the description carries the behavioral burden. It usefully discloses that cels are included and that placement is above the original, but it does not say whether the duplicate is selected afterward, how it is named, or what the result looks like.

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?

A single front-loaded sentence with no filler. The key behavioral facts, cels and placement, are stated immediately.

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 two-parameter mutation tool with no annotations and no output schema, the description covers the core effect but leaves both parameters undocumented and does not describe post-call state such as selection or duplicate naming. It is minimally adequate but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters. The description does not explain the required 'name' parameter or the optional 'file' parameter, so it does not compensate for the missing schema documentation.

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 (duplicate) and resource (layer) and adds the meaningful detail that cels are copied and the copy is placed above the original. It implicitly distinguishes itself from duplicate_frame and add_layer by naming 'layer', though it does not explicitly contrast with those siblings.

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?

There is no when-to-use guidance or comparison with alternatives such as add_layer, duplicate_frame, or merge_layer_down. The intent is inferable from the name, but the description gives no conditions, prerequisites, or exclusions.

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