Skip to main content
Glama
midarikawa

Aseprite MCP Tools

by midarikawa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_group

Create a new empty group layer in an Aseprite file to organize artwork. Optionally nest it under an existing group by name or group/subgroup path.

Instructions

Add a new, empty group layer.

Combine with add_layer(group=...) / duplicate_layer(group=...) to build a grouped layer structure.

Args: filename: Name of the Aseprite file to modify group_name: Name of the new group parent_group: Optional existing group to nest the new group inside, by name or "group/subgroup" path (default: top level)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
group_nameYes
parent_groupNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations provided, but the description is straightforward. It does not disclose potential side effects like name conflicts or overwriting behavior, leaving some behavioral gaps.

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

Conciseness5/5

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

The description is concise with two clear paragraphs, front-loading the main action and then detailing parameters efficiently.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with 3 parameters, the description covers the purpose, usage pattern, and parameter semantics completely. No output schema is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The Args section adds meaningful explanations for each parameter, including the default behavior of parent_group. Schema coverage is 0%, so the description compensates well.

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

Purpose5/5

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

The description clearly states 'Add a new, empty group layer' and explains how it integrates with add_layer and duplicate_layer, distinguishing it from sibling tools that add regular layers or duplicate layers.

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?

The description explicitly guides usage with add_layer/duplicate_layer and explains the parent_group parameter for nesting. However, it does not mention when not to use this tool or provide alternatives.

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