lentera-aseprite-mcp

export_godot_spriteframes

Convert a sprite sheet PNG into a Godot 4 SpriteFrames .tres resource for AnimatedSprite2D use.

Instructions

Generate a Godot 4 SpriteFrames .tres resource from a sprite sheet. Ready to use with AnimatedSprite2D.

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": {
      "sprite_sheet_path": "<sprite_sheet_path>",
      "output_path": "<output_path>"
    },
    "name": "export_godot_spriteframes"
  }
}

Input Schema

Name	Required	Description
`fps`	No	Animation FPS (default: 8 for walk cycle, 10-12 for attack)
`frame_width`	No	Width of each frame in pixels (default: sprite width)
`output_path`	Yes	Output path for .tres file (e.g. res://Assets/Sprites/Characters/Protagonist/protagonist.tres)
`frame_height`	No	Height of each frame in pixels (default: sprite height)
`sprite_sheet_path`	Yes	Path to the exported sprite sheet PNG

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 14, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool generates a resource, without mentioning whether it overwrites existing files, validates input paths, or handles errors. For a file-generating operation, these details are important and missing.

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?

The description is a single, concise sentence that front-loads the action ('Generate') and includes the key context (Godot 4, SpriteFrames, sprite sheet, AnimatedSprite2D). Every word earns its place, with no redundancy.

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 and schema together cover the core functionality and all parameters, but the lack of annotations and output schema leaves gaps such as overwrite behavior, expected sprite sheet format, and whether multiple animations are supported. It is adequate for a simple tool but not fully 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 100% with all five parameters described in the input schema. The description itself does not add any parameter-level semantics beyond the schema, so the baseline score of 3 applies.

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 the tool's function: generating a Godot 4 SpriteFrames .tres resource from a sprite sheet. It distinguishes itself from sibling export tools by specifying the exact output format and its intended use with AnimatedSprite2D, making it unambiguous.

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?

The description provides clear context for when to use this tool: when you need a Godot 4 SpriteFrames resource for AnimatedSprite2D. It does not explicitly mention alternatives or exclusions, but the specific mention of SpriteFrames and Godot 4 effectively narrows the use case among the sibling export tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.