Voidless

make_gif

Turn frames (or a sprite sheet) into an animated GIF: frame rate, loop, whole-number nearest-neighbour scale for crisp pixel art, transparency kept (GIF transparency is on/off per pixel), or flattened onto a background colour. Pixel art with up to 255 colours keeps every colour exactly. Images up to 2048x2048, 256 frames, 32 MB of input per call. Free: no credits.

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

Input Schema

Name	Required	Description
`fps`	No
`loop`	No
`save`	No	Also save the result to your Voidless library (free, private) and return its asset id and cdn.voidless.dev URL, for passing to the next tool without base64
`scale`	No	Nearest-neighbour upscale (2 = each pixel becomes 2x2)
`sheet`	No	Instead of frames: one sprite sheet image, cut into frames row by row.
`frames`	No	Frames in order, each an image (https URL, library image key, data: URI or base64). An animated GIF counts as all its frames.
`background`	No	Hex colour to flatten onto, e.g. #1a1a2e. Omit to keep transparency.
`sheet_rows`	No	Rows of the sheet (with sheet).
`sheet_columns`	No	Columns of the sheet (with sheet). Omit columns and rows to auto-detect the grid.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important operational traits: input limits (2048x2048, 256 frames, 32 MB per call), transparency behavior, exact colour preservation up to 255 colours, nearest-neighbour scaling, and that the call is free. These details materially help an agent anticipate behavior and constraints.

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 tightly written and front-loads the purpose immediately. Each sentence carries relevant information about capabilities, limits, or cost, with no filler.

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?

For a tool with nine optional parameters, no output schema, and rich annotations, the description covers purpose, constraints, transparency, scaling, and cost well. It does not describe the normal return format when save is false, which is a meaningful gap given the absence of an output schema.

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?

Schema coverage is 78%, so the schema already documents most parameters. The description still adds useful meaning by explaining crisp pixel-art scaling, per-pixel GIF transparency versus background flattening, and exact palette preservation for low-colour pixel art.

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 states a specific verb and resource: 'Turn frames (or a sprite sheet) into an animated GIF.' It is clear what the tool produces, but it does not explicitly differentiate itself from related siblings such as animate_sprite, generate_animation_set, or export_godot_spriteframes.

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?

Usage is implied by the conversion focus: use this when you already have frames or a sprite sheet and need a GIF. However, the description gives no explicit when-not guidance and never names alternatives such as animate_sprite or pack_sprite_sheet for comparison.

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

All Voidless tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?