Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

export_gamemaker

Exports Aseprite sprite strips for GameMaker, splitting frames into tag-based PNG strips, reporting per-strip FPS, and flagging uneven timing for correct sprite import.

Instructions

Write sprite strips GameMaker cuts up by itself: one <name>_<tag>_stripN.png per tag, or <name>_stripN.png with no tags. Drag them into GameMaker, or import them in its sprite editor. GameMaker gives a sprite one speed, so the result lists each strip's fps to enter there, and flags uneven timing. 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": {
      "output_dir": "<output_dir>"
    },
    "name": "export_gamemaker"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
nameNo
output_dirYes

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 supply openWorldHint and destructiveHint=false, so the description carries most of the burden and does well: it discloses that multiple files are written (one per tag), the exact filenames, and that the result reports per-strip `fps` and flags uneven timing because GameMaker allows one speed per sprite. It omits overwrite behavior for existing files and permission expectations.

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?

Front-loads the concrete output artifact, which is the highest-value information, and the sentences are dense with real content. The embedded filename markup is slightly noisy but not wasteful.

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?

Since there is no output schema, the description must convey results and does so via the fps listing and uneven-timing flags. However, for a file-writing exporter with a required directory argument, the absence of any statement about `output_dir` semantics or collision handling leaves a meaningful gap.

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 supply meaning; it explains `name` (filename prefix in the pattern) and `file` (headless mode). The required `output_dir` parameter is never mentioned — only implied by 'Drag them into GameMaker', which leaves a required argument undocumented.

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: writes GameMaker sprite strips with the exact naming convention (`<name>_<tag>_stripN.png`). The GameMaker target implicitly separates it from engine siblings like export_godot or export_unity_sprite, but the description never names those alternatives explicitly.

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?

'Drag them into GameMaker, or import them in its sprite editor' describes downstream consumption rather than when to pick this tool over sibling exports. The one real conditional is 'Headless: pass ``file``', which is useful but narrow. No when-not guidance is given.

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