Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

move_layer_to_group

Move a layer into a specified group in Aseprite to organize artwork, correct layer hierarchy, and keep pixel-art projects structured.

Instructions

Move a layer inside a layer group.

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": {
      "layer": "<layer>",
      "group": "<group>"
    },
    "name": "move_layer_to_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
groupYes
layerYes

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 supply only a title, so the description carries the full disclosure burden. It does not say which position the layer takes inside the group, whether the layer is removed from its prior parent, what happens if the group does not exist, or that this is a mutating operation — all essential for a reparenting tool.

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?

A single short sentence with no filler and the action front-loaded. It is efficient, though the extreme brevity reflects under-specification rather than disciplined editing.

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 mutating tool with no behavioral annotations, no output schema, and no schema parameter descriptions, one sentence is far from enough. An agent lacks the information needed to call it confidently or to predict the resulting layer ordering.

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%, and the description only implicitly maps to `layer` and `group`. It says nothing about `file`, which is optional with a null default, so the agent cannot tell whether omitting it targets the active file or some other 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?

The sentence names a specific verb ('Move') and specific resources ('a layer', 'a layer group'), so the action is unambiguous. It does not, however, distinguish this from the sibling `move_layer`, leaving the agent to guess which operation reorders layers versus which places them into a group.

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, when-not-to-use, or prerequisite context is given. With `move_layer` and `add_group` among siblings, the description should say that this tool reparents a layer rather than reordering it, but it supplies no such routing guidance.

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