Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

duplicate_frame

Creates a copy of a specified animation frame by its 1-based number, enabling quick repetition or variation of frames in an Aseprite project.

Instructions

Duplicate frame number (1-based).

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

Input Schema

NameRequiredDescriptionDefault
fileNo
numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/5.0
Behavior2/5

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

With only a title annotation and no safety/behavior hints, the description carries the full burden. It usefully discloses that 'number' is 1-based, avoiding an off-by-one error, but says nothing about where the copy is inserted (after the original vs. end of the timeline), whether the operation is undoable, or what permissions/state it requires.

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?

One short front-loaded sentence with zero filler. The brevity is appropriate, though the same terseness is what leaves the semantics thin.

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?

A mutation tool with no output schema, no behavioral annotations, and 0% schema coverage needs more than a single clause. Missing are the 'file' parameter's meaning, the insertion position of the duplicate, and any return information such as the new frame's index.

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%, so the description must compensate for both parameters. It clarifies the 1-based indexing of 'number', which adds real value, but leaves 'file' (nullable, defaults to null) completely unexplained — an agent cannot tell whether it names a project file, a sprite file, or defaults to the active document.

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+resource ('Duplicate frame') and ties it to the 'number' parameter, which cleanly separates it from add_frame, delete_frame and duplicate_layer. It stops short of any explicit comparison to sibling tools, so it is clear but not fully differentiated.

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 gives no when-to-use guidance, no preconditions (e.g. an existing file/document must be loaded), and no mention of alternatives such as add_frame. Everything beyond the verb is left to inference.

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