Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

export_sprite

Export active Aseprite sprites to PNG, GIF, or other extension-based formats, splitting multi-frame sprites into numbered images or an animated GIF. Returns written files without modifying the sprite.

Instructions

Export the active sprite to a file; format is chosen by out_path extension (.png, .gif, ...). A multi-frame sprite saved to a single-image format is split into <name>1.ext, <name>2.ext, ...; a multi-frame sprite saved to .gif becomes one animated GIF (all frames, honoring per-frame durations). The returned files lists what was actually written. Does not modify the sprite. 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_path": "<out_path>"
    },
    "name": "export_sprite"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
out_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare destructiveHint=false and openWorldHint=true; the description adds real substance beyond them — multi-frame sprites fan out to numbered files, .gif becomes one animated GIF honoring per-frame durations, and the 'files' return lists what was written. 'Does not modify the sprite' usefully confirms the non-destructive hint. Minor gap: it never mentions overwrite behavior when target files exist.

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?

Dense and front-loaded: the core action and format rule come first, then the frame-splitting consequences, then the return value, then a headless note. No filler sentences, though the final 'Headless: pass file.' is so compressed it reads as a fragment rather than guidance.

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?

With no output schema, the description correctly covers the return shape ('files' lists what was written), and it explains the frame-splitting outcomes that would otherwise surprise an agent. However, for a 2-param tool with 0% schema coverage, the unexplained `file` parameter and absent overwrite/error behavior leave the definition short of complete.

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 coverage is 0%, so the description must carry both parameters. It does explain out_path's semantics (extension selects the format), but 'Headless: pass file' is opaque — it never says what `file` should contain or how it relates to out_path, leaving one of two parameters under-specified.

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 ('Export the active sprite to a file') and adds the decisive detail that the output format is inferred from the out_path extension. It does not distinguish itself from plausible siblings such as export_spritesheet, export_layers, or the engine-specific exporters, so an agent still has to guess which export tool to reach for.

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 is only implied: the extension-based format rule and 'Headless: pass file' tell an agent how to call it, but nothing says when to prefer this over export_spritesheet, export_animation, or batch_export. No exclusions or prerequisites are stated.

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