Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

export_godot

Exports a horizontal sprite sheet with a Godot 4 SpriteFrames .tres, creating one animation per tag while preserving frame timing, direction, and repeat count.

Instructions

Export a horizontal sprite sheet AND a Godot 4 SpriteFrames .tres beside it, with one animation per tag, keeping each frame's timing, the tag's direction, and its repeat count. No tags gives one looping default animation. Export inside a Godot project and the res:// path is worked out from project.godot; otherwise project_found is false and the file must sit at the project root. For sharp pixels, set the node's Texture Filter to Nearest. 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": {
      "png_path": "<png_path>"
    },
    "name": "export_godot"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
png_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the sparse annotations, it explains the output files, per-tag animation behavior, timing/direction/repeat-count preservation, the default looping animation when no tags exist, and project path resolution. It does not disclose overwrite behavior or error handling, so it is strong but not exhaustive.

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 front-loaded with the primary export behavior and remains reasonably compact. The sharp-pixel texture-filter tip is useful but slightly tangential, keeping it short of perfect conciseness.

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

Completeness4/5

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

For a two-parameter export tool with no output schema and minimal annotations, it covers the important artifacts, tag handling, Godot project detection, and headless mode. The main remaining gap is that parameter semantics, especially png_path, are not complete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It only hints that file should be passed in headless mode, while the required png_path parameter is never explicitly described in format or path semantics.

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 states a specific export action and names the exact artifacts: a horizontal sprite sheet plus a Godot 4 SpriteFrames .tres file. The Godot-specific .tres output distinguishes it from generic sprite-sheet or animation export siblings.

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?

It gives clear usage context: export inside a Godot project for res:// path resolution, otherwise the file must sit at the project root, and headless use requires passing file. It does not explicitly compare against sibling export tools, but it does not mislead about when the tool applies.

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