Rengi Forge

sprite_tools_pixelate

Clean pixel art: find the true pixel grid, downscale to it, snap to a palette, hard alpha. Price: $0.10 USDC via x402, charged only on success. Part of Sprite tools: 2D sprite jobs for games: cut sprites out of their background (exact for one-color backgrounds, AI for busy ones), turn animation videos into aligned sprite sheets, make normal maps for 2D lights, build 47-tile autotile sets with Tiled, Godot and Unity rules, slice a sheet into frames, pack frames into an atlas with TexturePacker and Unity metadata, and turn upscaled or AI-generated pixel art into real pixel art on its true grid with a limited palette..

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sprite_tools_pixelate"
  }
}

Input Schema

Name	Required	Description
`image`	No	Base64 PNG, JPEG or WebP.
`scale`	No	Size of one art pixel in image pixels; detected when omitted.
`colors`	No
`palette`	No	Hex colors to snap to.
`imageUrl`	No
`alphaThreshold`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026
- changedInput schema / properties / image / description
```
Previous value: -"Base64 PNG."New value: +"Base64 PNG, JPEG or WebP."
```
First observedOct 20, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does add genuinely useful non-schema context: pricing ($0.10 USDC via x402) and the important billing guarantee 'charged only on success.' It still says nothing about what the tool returns (image vs. URL) or whether the operation is reversible/idempotent.

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

Conciseness2/5

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

The first sentence and the pricing clause are well front-loaded and earn their place, but roughly half the text is a catalog of all sibling Sprite tools rather than anything about this tool, which is padding for the selection decision at hand.

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?

For a 6-parameter, zero-required mutation-ish image tool with no annotations, no output schema, and 50% schema coverage, the description should clarify parameter behavior and return shape; instead it spends its budget on a family overview, leaving real gaps.

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 50%: colors, imageUrl, and alphaThreshold are undocumented in the schema and unaddressed in the description. 'Snap to a palette' and 'hard alpha' loosely gesture at palette/alphaThreshold but add no format, range, or default semantics over the schema.

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 opening sentence gives a specific verb+resource with concrete sub-actions (find the true pixel grid, downscale, snap to a palette, hard alpha), which is enough to separate it from sprite_tools_normal_map, sprite_tools_autotile, and sprite_tools_slice. It does not explicitly say what it is not, but the operation is unambiguous.

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

Usage Guidelines3/5

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

There is no explicit when-to-use/when-not statement or named alternative. Usage is only implied at the tail ('turn upscaled or AI-generated pixel art into real pixel art'), which suggests a context but leaves the agent to infer it rather than routing deliberately.

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

All Rengi Forge tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?