Skip to main content
Glama
Sign In
Aseprite MCP Tools

Aseprite MCP Tools

by ZeroTian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

export_spritesheet

Combine animation frames into a sprite sheet image and optionally generate a JSON metadata file.

Instructions

Export frames as a sprite sheet, optionally with a JSON data file.

Args: filename: Aseprite file to export output_filename: Output sheet image path (PNG) sheet_type: Layout: "horizontal", "vertical", "rows", "columns", or "packed" data_filename: Optional path for a JSON metadata file (json-array format) scale: Integer scale factor applied before packing (default 1) padding: Padding in pixels between frames (default 0) tag_name: Only include frames of this animation tag (default: all frames)

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>",
      "output_filename": "<output_filename>"
    },
    "name": "export_spritesheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
output_filenameYes
sheet_typeNohorizontal
data_filenameNo
scaleNo
paddingNo
tag_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention side effects (e.g., file overwriting, file locking), error conditions (e.g., missing file, invalid sheet type), or whether the operation is read-only or modifies the original file. This lack of behavioral context leaves the agent underinformed.

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?

The description is a compact docstring with a two-line intro followed by a bulleted Args list. Every sentence is informative with no filler. Slight improvement would be possible by grouping similar parameters, but overall it is well-structured and efficient.

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?

The description covers parameter semantics decently but lacks behavioral details like error handling, file overwrite behavior, and the structure of the optional JSON output. Given the absence of annotations and output schema, more contextual information would help the agent fully understand the tool's effects and constraints.

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?

Schema description coverage is 0%, so the description carries the full burden. It explains each parameter: filename (input file), output_filename (PNG path), sheet_type (layout options), data_filename (optional JSON), scale, padding, and tag_name. However, sheet_type options ('horizontal', 'vertical', 'rows', 'columns', 'packed') are listed without explanation of differences, slightly reducing clarity.

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 'Export frames as a sprite sheet, optionally with a JSON data file.' This is a specific action (export) on a specific resource (frames) to produce a sheet, distinguishing it from sibling tools like export_frame, export_layers, and export_sprite.

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 provides a list of parameters but does not include any explicit guidance on when to use this tool versus its alternatives (e.g., export_frame, export_layers). There is no mention of prerequisites, limitations, or conditions that favor this tool.

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