Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

add_frame

Append a new empty frame to an Aseprite animation, optionally targeting a specific file, to extend a sprite timeline for further drawing or editing.

Instructions

Append a new empty frame.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.4/5.0
Behavior2/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 burden and discloses almost nothing: no mention of where the frame is appended (end of timeline? after selection?), whether it mutates state, or what happens on undo. 'Empty' is the only behavioral detail provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler, so it is tight; however, the brevity reflects under-specification rather than efficiency.

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 annotations, no output schema, and an undocumented parameter, the description should say where the frame lands and what is returned (e.g., new frame index). It omits all of that.

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

Parameters1/5

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

Schema coverage is 0% and the description never mentions the single 'file' parameter, leaving its role (target file? source file?) entirely undefined. The structured schema offers only the bare property name with a null default, so nothing compensates.

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 a new empty frame'), which is clear enough. It does not distinguish itself from the sibling 'add_frames' (plural), so the agent cannot tell from the text which one to pick.

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 indication of when to use this versus 'add_frames', 'add_layer', or 'duplicate_frame'. No prerequisites or context about which document/timeline the frame is appended to.

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