Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

add_group

Create a layer group in an Aseprite file to organize sprites. Move layers into the group afterward and reference nested layers by name or as Group/Layer paths.

Instructions

Add a layer group. Move layers into it with move_layer_to_group; reference nested layers anywhere by name or as Group/Layer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior2/5

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

The only annotation is a title, so the description carries the full behavioral burden. It usefully discloses the Group/Layer addressing convention, but says nothing about whether the group is created empty, how duplicate names are handled, or what the tool returns. Critically, both parameters are optional, yet the description never explains what happens when name or file is omitted.

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, front-loaded sentences with the primary action first and the workflow hint second. The reStructuredText double-backtick markup adds minor visual noise but no real bloat.

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 simple two-parameter creation tool with no output schema this covers the essential addressing model, which is the most valuable piece of context. It remains incomplete on parameter meaning ("file") and on edge-case behavior when optional parameters are null.

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 compensate and it largely does not. "name" can be inferred as the group name from the surrounding text, but "file" is never mentioned at all, leaving an unnamed and unexplained parameter in a two-parameter tool.

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 ("Add a layer group") and clarifies the follow-on operation via the named sibling move_layer_to_group. It does not explicitly contrast with the sibling add_layer, but the group-vs-layer distinction is clear from the wording itself.

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

Usage Guidelines4/5

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

Tells the agent what to do next (move layers in via move_layer_to_group) and how to address nested layers by name or Group/Layer path, which is a genuine usage rule. It stops short of stating exclusions, such as when to prefer add_layer or what happens if a group with the same name exists.

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