Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

rename_layer

Idempotent

Change a layer's name in an Aseprite file by specifying the current name and the new name, keeping layer stacks clear for pixel art editing and export workflows.

Instructions

Rename a layer.

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_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
new_nameYes
old_nameYes

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 supply only idempotentHint=true; there is no destructive hint or readOnly hint. The description adds no behavioral context: it does not say what happens if old_name is not found, whether the rename is reversible, or what scope the operation applies to. Given the thin annotation coverage, the description should have carried more weight.

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 short sentence with zero filler is front-loaded, but its brevity comes at the cost of under-specification rather than true conciseness. It does not waste words, but it also does not earn its place beyond restating the tool name.

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?

This is a mutation with three parameters, no output schema, no parameter documentation, and only an idempotency annotation. For a state-changing operation the definition is incomplete: it omits failure modes, scope of the 'file' parameter, and return behavior.

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% for all three parameters. The description does not clarify old_name vs new_name semantics, nor does it explain the optional 'file' parameter and what a null default means (current document vs. a named file). The parameter names are largely self-explanatory, but the meaning of 'file' remains ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource ('Rename a layer'), which is enough to tell it apart from siblings like rename_tag or delete_layer by resource. However, it adds no scope information such as which layer set, which file, or how the layer is identified, so it is only minimally viable.

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?

There is no when-to-use guidance, no prerequisites (e.g., the layer must already exist), and no mention of alternatives such as duplicate_layer plus delete_layer. The agent must infer everything from the name.

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