Voidless

day_night_palettes

Grade a sprite, tile or scene to dawn, day, dusk and night, like the Day/Night Palette tool on voidless.dev/tools. Each colour maps to exactly one new colour, so pixel art keeps its palette size, and the reply lists every from→to pair per time of day: a palette swap an engine can apply at runtime. Optional: keep bright saturated colours lit at night (windows, torches), and a looping day-cycle GIF. Images up to 2048x2048, 256 frames, 32 MB of input per call. Free: no credits.

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": {
      "image": "<image>"
    },
    "name": "day_night_palettes"
  }
}

Input Schema

Name	Required	Description
`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
`image`	Yes	An image: an https URL (e.g. a cdn.voidless.dev link from get_asset or a saved result), a library image key (assets/…png, as get_asset lists it), a data: URI, or base64 PNG/GIF.
`times`	No
`lights`	No	Keep bright, saturated colours lit at night (lit windows, torches, crystals)
`cycle_frames`	No	Also return a looping day→dusk→night→dawn GIF with this many frames (0 = none)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond the annotations, it discloses that each colour maps one-to-one, output lists per-time from→to pairs, optional lights behavior, GIF generation, image limits (2048x2048, 256 frames, 32 MB), and no credit cost. It still does not fully describe all response fields or save/library side effects.

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 front-loaded with purpose, then output behavior, options, limits, and cost. It uses four efficient sentences with no material redundancy.

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?

With no output schema, the description carries the return-value burden; it explains palette pair lists and optional GIF output, plus input size limits. It does not fully specify the response structure, such as whether transformed images are returned alongside palettes, leaving a minor but real gap.

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 80%, so the baseline is 3; the description adds meaning for 'times' (dawn/day/dusk/night), 'lights' (bright saturated colours stay lit at night), and 'cycle_frames' (looping day-cycle GIF). It adds no semantic detail for 'save', which is already covered by 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 description states a specific verb and resource ('Grade a sprite, tile or scene') and scope to dawn, day, dusk and night. It makes the time-of-day transform reasonably clear, but it does not explicitly differentiate from siblings such as palette_swap or match_palette.

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?

It implies the tool is for producing day/night variants and mentions optional lights and GIF output, but never states when to choose it over alternatives. Usage is inferable from purpose rather than explicitly guided.

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?