Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

rename_tag

Idempotent

Rename an animation tag from its old name to a new one in Aseprite, with an optional file for headless edits and a single undo step.

Instructions

Rename the animation tag old_name to new_name. One undo step. Headless: pass file.

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": {
      "old_name": "<old_name>",
      "new_name": "<new_name>"
    },
    "name": "rename_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
new_nameYes
old_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare idempotentHint=true, so the description carries most of the behavioral burden. It adds two concrete traits beyond the annotations: the rename counts as exactly 'One undo step' (interacts with the undo sibling), and headless operation requires passing file. It doesn't say what happens when old_name is absent, which keeps it from a 5.

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?

Three short sentences, zero filler, with the core operation front-loaded and the conditional headless note placed last. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter mutation with no output schema, the description covers the action, the undo consequence, and the headless requirement. Missing only edge-case behavior (nonexistent tag name, error signalling), which is minor at this complexity.

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 description coverage is 0%, so the description must compensate and it does so partially: old_name/new_name semantics are clear from the rename phrasing, and file is explained as a headless-mode argument. It never says what file should contain (a path? a project file?) or whether tags are matched case-sensitively.

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: 'Rename the animation tag'. Naming 'animation tag' plus the old_name/new_name mapping makes it distinguishable from siblings like rename_layer or create_tag without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the operation itself (rename an existing tag), and the 'Headless: pass file' note signals a context-dependent invocation mode. There is no explicit when-to-use versus alternatives guidance and no stated prerequisite such as the tag already existing.

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