Skip to main content
Glama

Image to pixel art

pixelate_image

Turn a photo or illustration into pixel art: shrink it to a pixel grid and reduce it to a few colours (or a named palette). Returns the PNG.

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": "pixelate_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoNearest-neighbour upscale of the returned PNG, capped at 1024 px
widthNoWidth of the pixel grid in pixels (height keeps the aspect ratio)
colorsNoNumber of colours when no palette is given
paletteNoPalette id (e.g. pico-8, game-boy-dmg, cga-16, sweetie-16; see list_palettes) or hex colours like "#1a1c2c,#5d275d"
image_urlNoPublic http(s) URL of a PNG or JPEG (max 4 MB, 2048x2048)
image_base64NoPNG or JPEG as base64 (or a data: URL), if there is no public URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / palette / description
      Previous value: -"Palette name (pico-8, sweetie-16, endesga-32, game-boy, 1-bit) or hex colours like \"#1a1c2c,#5d275d\""New value: +"Palette id (e.g. pico-8, game-boy-dmg, cga-16, sweetie-16; see list_palettes) or hex colours like \"#1a1c2c,#5d275d\""
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the core transformation and the output format ('Returns the PNG'), but omits failure behavior, input size limits (the schema carries the 4 MB / 2048x2048 caps), palette-lookup validation, and what happens when neither image field is populated.

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?

A single front-loaded sentence with a colon introduces the verb and resource first, then the pipeline steps, then the return value. No filler or redundancy; every clause carries information.

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?

With 6 parameters, zero required fields, full schema coverage, and no output schema, the description is adequate but leaves a real gap: it never explains that an image source must be supplied despite nothing being marked required, nor how palette and colors interact when both are given. Acceptable minimum, but an agent could call it incorrectly.

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 each parameter is already documented with defaults, ranges, and units. The description reinforces the relationship between width and colour reduction and the palette alternative but adds no syntax, precedence, or edge-case meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Turn a photo or illustration into pixel art') plus the mechanism (shrink to a pixel grid, reduce to a few colours or a named palette) and the return type (PNG). It does not name the contrasting sibling 'upscale_pixel_art', so an agent must infer the direction distinction itself.

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?

There is no when-to-use or when-not-to-use guidance and no routing to alternatives such as upscale_pixel_art, extract_palette, or list_palettes even though the description references named palettes. Crucially, it never states that exactly one of image_url or image_base64 must be supplied, which is the main selection decision the caller faces.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources