Skip to main content
Glama

export_game_asset_bundle

Export a sprite into a game-ready bundle with flattened PNG, animated GIF, sprite sheet with JSON, per-tag GIFs, and manifest.

Instructions

Export a sprite into a game-ready bundle directory: a flattened PNG, an animated GIF, a packed sprite sheet (+ JSON data), a GIF per animation tag, and a manifest.json describing everything.

Args:
    overwrite: Replace existing bundle files (default False = no-clobber). Every
        planned output is checked up front, so the bundle fails before writing any
        file if a target already exists.

Returns a ``workflow_manifest.v1`` manifest (the same object is also written to
disk as manifest.json inside the bundle).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleNo
filenameYes
overwriteNo
bundle_nameNo
Behavior4/5

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

With no annotations, the description must reveal behavioral traits. It explains overwrite behavior (no-clobber, pre-check) and that a manifest is returned. However, it omits potential side effects (e.g., file system writes) and permissions, but for an export tool, this is acceptable.

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 main purpose and lists outputs concisely. It uses a bullet-like structure with Args and Returns, but is slightly verbose. Overall, it efficiently conveys necessary information.

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?

Given the tool's complexity (4 parameters, no output schema), the description covers the main outputs and the overwrite behavior well. It mentions the manifest return but does not detail its structure. However, for an experienced agent, the description is mostly sufficient to use the tool correctly.

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?

With 0% schema description coverage, the description should explain all parameters. It only details 'overwrite'; 'filename', 'scale', and 'bundle_name' are not explicitly described beyond their schema titles. The parameter names are somewhat self-explanatory, but the description fails to fully compensate for the lack of schema descriptions.

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 exports a sprite into a game-ready bundle directory and lists specific outputs (PNG, GIF, spritesheet, etc.), distinguishing it from sibling export tools that produce single formats.

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 implies this is a comprehensive export for game-ready assets, but does not explicitly contrast with siblings or state when an alternative (e.g., export_png) is preferred. The context is clear enough for an agent to infer usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MalloyTheDev/aseprite-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server