pixelart-mcp

Overview Schema Source Related Servers Discussions Admin

pixel_export_gif

Idempotent

Combine same-size canvas PNGs into a looping animated GIF. Supports per-frame durations, ping-pong playback, and transparency preservation.

Instructions

Combine same-size canvas PNGs into a looping animated GIF.

Frames play in the order given at duration_ms per frame (or per-frame durations_ms). ping_pong=true plays forward then backward for seamless bounce/idle loops. Transparency is preserved as GIF binary transparency (alpha <= 128 becomes transparent). Source canvases are untouched. Returns JSON {"exported", "frames", "frames_played", "scale", "width", "height"}. On failure returns "Error: ...".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description adds behavioral details beyond annotations: 'Transparency is preserved as GIF binary transparency (alpha <= 128 becomes transparent). Source canvases are untouched.' It also describes the return JSON structure and error format, which aligns with idempotentHint=true and destructiveHint=false.

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 concise and front-loaded: the first sentence states the main purpose, followed by brief clarifications on behavior and return values. No extraneous text.

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?

The description covers key aspects: input constraints, transparency behavior, return format, and error handling. However, it omits details on the scale parameter and out_path validation, which are present in the schema but not reinforced.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage in the context signal, the input schema itself contains detailed descriptions for all properties (e.g., scale, duration_ms). The tool description adds clarity by explaining the role of ping_pong and per-frame durations, complementing the schema.

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's purpose: 'Combine same-size canvas PNGs into a looping animated GIF.' It specifies the action (combine), input (canvas PNGs), and output (GIF), distinguishing it from sibling tools like pixel_export_png and pixel_export_spritesheet.

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 explains when to use parameters like ping_pong for idle/bounce loops and notes that source canvases are untouched. However, it does not explicitly compare against alternatives like pixel_export_spritesheet or state when not to use this tool, so it lacks explicit exclusions.

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