Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

create_tag

Creates a named animation tag spanning a specified 1-based frame range in an Aseprite file, organizing sprite animation segments for editing or export.

Instructions

Create an animation tag named name spanning frames from_frame..to_frame (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": {
      "name": "<name>",
      "from_frame": "<from_frame>",
      "to_frame": "<to_frame>"
    },
    "name": "create_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
nameYes
to_frameYes
from_frameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/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 for a mutation tool. It discloses the useful 1-based frame indexing convention but says nothing about behavior on duplicate tag names, whether referenced frames must already exist, or how the target file is chosen.

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?

One sentence, front-loaded with the verb and resource, no filler. The frame-range detail is placed where it is immediately useful.

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 4-parameter mutation tool with no annotations, no output schema, and undocumented schema fields, the definition is too thin. It omits the `file` target, duplicate-name behavior, and any indication of what is returned.

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 coverage is 0%, so the description must compensate and it partially does: it maps name, from_frame and to_frame to their meaning and clarifies the 1-based indexing. The fourth parameter, `file`, is never explained even though it presumably selects which sprite/document the tag belongs to.

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 ('Create an animation tag') plus the exact frame span it covers, which is enough to separate it from rename_tag/delete_tag/set_tag_range siblings. It stops short of explicitly naming those alternatives.

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, no prerequisites, and no mention of the sibling tools that modify tags after creation. The agent must infer the workflow entirely.

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