Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

add_frames

Append a specified number of empty frames to an Aseprite animation in a single undo step, enabling quick timeline expansion without multiple history entries.

Instructions

Append count empty frames in one undo step.

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

Input Schema

NameRequiredDescriptionDefault
fileNo
countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears the full behavioral burden; it does add one genuinely useful trait — all frames land in a single undo step, i.e. atomic, one-shot reversibility. It does not say where the frames are appended, whether they are selected afterwards, what the file parameter scopes, or how the new frames are identified in the result.

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 zero filler. The quantity and the atomicity guarantee are the two things an agent needs and both are stated compactly.

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?

For a mutation tool with no meaningful annotations, no output schema, and 0% schema coverage, the description is too thin. It should clarify the file default, what 'empty' means, and where the frames are inserted to be callable with confidence.

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. It gives meaning to count ('count empty frames') but leaves the optional file parameter — with a null default — entirely unexplained, so the agent cannot tell whether omitting it targets the active document or fails.

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 and resource — 'append empty frames' — plus the quantity, which distinguishes it from the singular sibling add_frame by implying a batch of frames at once. It stops short of explicitly saying it operates on the end of the current animation/layer, so a small inference is still required.

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 when-to-use guidance at all: nothing says when to prefer this over add_frame or tween_frames, and no prerequisites are mentioned. The agent must infer from the plural name and the count parameter that this is the batch variant.

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