Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

move_layer

Reorder a layer within the stack by specifying up, down, top, or bottom direction, so you can change draw order and layer organization in Aseprite.

Instructions

Reorder a layer in the stack. direction is up | down | top | bottom (bottom = stack index 1).

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>",
      "direction": "<direction>"
    },
    "name": "move_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
nameYes
directionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior3/5

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

Annotations contain only a title, so the description carries the full disclosure burden; 'reorder' does signal a mutation of document state. It adds genuinely useful behavioral detail about the direction values and the index base ('bottom = stack index 1'), but says nothing about effect on other layers' indices, failure when the layer is missing, or reversibility.

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

Conciseness4/5

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

Two short sentences, front-loaded with the action, with no filler. The backtick formatting of ``direction`` is slightly awkward but costs no clarity.

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

Completeness3/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 only a title annotation, the description covers the interesting enum but omits the meaning of `file`, the layer-resolution behavior for `name`, and any error/edge-case behavior. It is minimally adequate rather than complete.

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%, so the description must define all three parameters. It does a good job on `direction` (enumerating up/down/top/bottom and defining the index base) but leaves `name` and the optional `file` completely unexplained — notably what `file` refers to or whether omitting it targets the active document.

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 ('Reorder') and resource ('a layer in the stack'), which cleanly separates it from siblings like rename_layer, delete_layer, or set_layer_opacity. It stops short of naming the closest alternative, move_layer_to_group, so the distinction requires the agent to infer it.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as move_layer_to_group for moving a layer into a group. The stack-reordering context is implied, but an agent must infer which sibling to pick.

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