Skip to main content
Glama
Sign In
Aseprite MCP

Aseprite MCP

by MalloyTheDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rename_layer

Rename an Aseprite layer by providing the filename, layer identifier, and new name to let AI agents update sprite layer labels during editing.

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": {
      "filename": "<filename>",
      "layer": "<layer>",
      "new_name": "<new_name>"
    },
    "name": "rename_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerYes
filenameYes
new_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.10.0
    • removedInput schema / properties / filename / title
      Removed value: -"Filename"
    • removedInput schema / properties / layer / title
      Removed value: -"Layer"
    • removedInput schema / properties / new_name / title
      Removed value: -"New Name"
    • removedInput schema / title
      Removed value: -"rename_layerArguments"
  2. First observedv0.7.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already disclose readOnlyHint=false and openWorldHint=false, so the mutation nature is covered structurally. The description adds nothing beyond that: it does not say what happens on name collision, whether the old name is preserved, or what errors can occur. For a mutating tool, this leaves the behavioral profile thin.

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?

A single short sentence with zero waste and the action front-loaded, but the brevity reflects under-specification rather than efficient conciseness.

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 three-parameter mutation tool with no output schema and zero parameter documentation, the description is too thin to be complete. It should at least clarify parameter roles, uniqueness/error behavior, or prerequisites.

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?

All three parameters (filename, layer, new_name) have 0% schema description coverage, so the schema carries no semantics and the description must compensate — but it provides none. The names are largely self-explanatory, which keeps this above a 1, but there is no explanation of format or constraints.

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 (rename) and resource (layer), so the agent knows exactly what operation this performs. However, it offers no differentiation from near-siblings like set_layer_properties or move_layer, which also alter layer metadata.

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?

The description gives no indication of when to use this tool versus alternatives such as set_layer_properties, nor any preconditions (e.g., layer must exist, name must be unique). Usage is left entirely to inference.

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