Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

export_layers

Export each image layer, including grouped and hidden layers, as separate PNGs. Multi-frame sprites split per frame, visibility is restored, and passing a file enables headless export.

Instructions

Export every image layer (recursing into groups) as its own PNG in out_dir, named <sanitized-layer-name>.png. Hidden layers are exported too; every layer's original visibility is restored afterwards, so the document ends exactly as it started. A multi-frame sprite splits each layer into <name>1.png, <name>2.png, ...; the returned files lists what was actually written. Headless: pass file.

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": {
      "out_dir": "<out_dir>"
    },
    "name": "export_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
out_dirYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the meaningful behaviors: files are written into out_dir, hidden layers are exported, visibility is restored so the document is unchanged, multi-frame sprites produce numbered files, and a files list is returned. That is substantial operational context even though openWorldHint is already declared. It does not mention failure modes (e.g., missing out_dir, unwritable paths).

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?

Four compact sentences, front-loaded with the core action, then naming convention, then side-effect guarantees, then the headless note. No filler and nothing repeated from the schema.

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 two-parameter tool with no output schema and no param descriptions, the description covers destination, input source, naming, multi-frame splitting, the return value ('files'), and the non-destructive visibility restore. An agent could call this correctly without any other information.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden and does so: out_dir is the destination directory for the generated PNGs, and file is the headless document input. It also explains the derived filename convention, which is not expressible in the schema at all.

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 description gives a specific verb and resource ('export every image layer ... as its own PNG') plus the group-recursion scope, which clearly separates it from spritesheet or animation exporters. It never names a sibling tool, so the differentiation is inferred from the output shape rather than stated.

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

Usage Guidelines3/5

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

Usage context is implied through the mechanics ('Headless: pass file'), which tells the agent when the file argument is required. There is no explicit when-to-use/when-not guidance relative to export_spritesheet, export_animation, or batch_export, leaving the choice to the agent's inference.

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