Skip to main content
Glama

forge_item_kit

Generate multiple pixel art sprites in a single batch on a shared grid for visual consistency, then split into individual PNGs—ideal for item sets, inventory icons, and collectibles.

Instructions

Generate multiple pixel art sprites in a single batch. Items are generated together on a grid for visual consistency, then split into individual PNGs. Ideal for item sets, inventory icons, collectibles, or any group of related sprites.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoTarget sprite size in pixels (default: 48). Snaps to nearest standard size.
itemsYesList of item descriptions (max 16). E.g. ["red apple", "banana", "cherry", "grapes"]
modelNoModel alias or full ID. Aliases: 25, nano-banana, banana, banana-2, nano-banana-2, gemini-flash, flash, gemini-pro, pro, gemini-25, gemini-flash-25 (default: nano-banana)
namesNoCustom file names for each item (default: item-0, item-1, ...)
styleNoVisual style preset (default: clean)
squareNoPad each item to square (default: true)
backgroundNoBackground color for generation. Use "auto" to pick based on items. (default: black)
referencesNoPaths to existing PNG/JPEG assets to match visual style.
outputPrefixYesOutput path prefix — items saved as {prefix}-{name}.png (e.g. "public/assets/items/fruit")
Behavior3/5

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

With no annotations, the description carries the burden. It discloses that items are generated together on a grid, split into individual PNGs, and assures visual consistency. However, it does not mention side effects like file overwriting or cleanup behavior, leaving some gaps.

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 three sentences with no waste: main action, process, and use cases. Information is front-loaded and every sentence contributes meaning.

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 has 9 parameters and no output schema, the description adequately explains the core workflow (batch generation, grid, split). It mentions the output as PNGs and covers use cases, though it could clarify that the grid is not saved as a separate artifact.

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 description coverage is 100%, so parameter meanings are already well-documented. The description adds context about batch generation and grid alignment but does not elaborate on specific parameters beyond what the schema provides.

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 starts with 'Generate multiple pixel art sprites in a single batch,' clearly stating the verb, resource, and scope. It distinguishes itself from siblings like forge_sprite (single sprite) and forge_tileset by emphasizing batch generation and splitting into individual PNGs.

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 explicitly states use cases: 'Ideal for item sets, inventory icons, collectibles, or any group of related sprites.' This provides clear context for when to use the tool, though it does not explicitly mention alternatives or exclusions.

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/freema/pixelforge-mcp'

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