Skip to main content
Glama

Generate Cocos Sprite Grid Sheet

asset_forge_generate_sprite_grid_sheet

Generate a sprite grid sheet to maintain character consistency across frames, slice into animation cells, and produce Cocos-ready metadata with alpha cleaning.

Instructions

Generate one AI contact sheet such as 3x3 or 4x3 for better character consistency, slice it into frames, clean alpha, and pack Cocos-ready sprite sheet metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesHuman-readable asset name. Used for file names after slugification.
rowsNo
seedNo
styleNoVisual or audio style, e.g. 'cozy pixel art', 'hand-painted fantasy', '8-bit arcade'.
actionNoidle
marginNo
promptYesDescribe the same character/object and the complete motion/state set.
columnsNo
paddingNo
frameSizeNo
outputDirNoDirectory where generated files should be written. Defaults to server config.
frameCountNo
postprocessNo
referenceImageUrlNoPublic reference image URL for image-to-image/edit capable providers.
referenceStrengthNoHow strongly an image-to-image/edit provider should preserve the reference.
referenceImagePathNoLocal reference image path for image-to-image/edit capable providers.
contactSheetBackgroundNoflat_key_color
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions actions like 'clean alpha' and 'pack metadata' but does not disclose side effects, file creation details, or whether the tool modifies existing files. The behavioral impact is under-described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that packs multiple processing steps, making it slightly run-on. It is adequately sized but could be more front-loaded and concise. Every part earns its place, but structure could be improved.

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

Completeness2/5

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

With 17 parameters, no output schema, and no annotations, the description is insufficient. It does not explain the output format, required parameter roles (beyond prompt/name), or describe defaults like frameSize, postprocess, etc. The tool's complexity demands more context.

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 only 41%, meaning most parameters lack descriptions. The tool description adds no parameter-specific information beyond mentioning '3x3 or 4x3' (related to rows/columns). It does not compensate for the low schema coverage.

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?

The description specifies generating an AI contact sheet for character consistency, slicing into frames, cleaning alpha, and packing Cocos-ready metadata. This clearly identifies the tool's purpose, but it does not distinguish from sibling 'asset_forge_generate_sprite_sheet', which may cause confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like 'asset_forge_generate_sprite_sheet' or 'asset_forge_generate_sprite'. The description implies use for multi-frame character consistency but offers no exclusions or prerequisites.

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/lightblink/cocos-asset-forge-mcp'

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