Skip to main content
Glama
Sign In

Voidless

by dev.voidless
OverviewDiscussionsAdmin

resize_sprite

Free. Only for images generated in Voidless (not uploads): pixel sprites of size 32, 48, 64, 96, 128, 192, 256 or 384, or HD (non-pixel, square 512/1024) images. Re-runs Voidless's pixel pass at a new size from the art it stored, so the base image, its rotations, edits and every animation come out at the new size on one palette and the character keeps its design (unlike generating it again smaller). On an HD image it makes a pixel version at size: generate HD, then resize to 64 and to 32 for pixel versions. Makes a NEW asset; the original is untouched.

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": {
      "id": "<id>"
    },
    "name": "resize_sprite"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAsset ID (from list_assets / get_asset or a previous result)
sizeNoNew size in px: 32, 48, 64, 96, 128, 192, 256 or 384. Omit to keep the size (required for an HD image)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (non-read-only, non-idempotent, non-destructive, closed-world), the description discloses that the operation is free, that it is non-destructive because it creates a NEW asset and leaves the original untouched, and that the base image, rotations, edits and all animations are re-rendered on one palette. That is exactly the behavioral context an agent needs before committing to a mutation.

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

Conciseness4/5

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

Front-loaded with the most decision-relevant facts ('Free.' then the eligibility constraint), and most sentences carry distinct information. There is mild redundancy in repeating the full size enumeration that the schema's const list already encodes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, no-output-schema tool, the description covers eligibility, effect, non-destructiveness, palette/animation propagation, the HD special case, and the omission default. An agent can decide and call correctly with nothing else.

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 100%, so baseline is 3; the description earns extra by giving meaning to the size choice — the allowed source sizes, that omitting size keeps the current size, that size is required for HD images, and why one would pick 64 versus 32 for pixel versions of an HD sprite. It does not describe the `id` parameter beyond what the schema already says.

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 uses a precise verb-plus-resource ('Re-runs Voidless's pixel pass at a new size') and explains the mechanism: it re-derives art from stored data rather than generating fresh. It also carves out the distinct case of HD images producing a pixel version, so the agent understands both modes without opening the schema.

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?

Strong preconditions are stated up front: only Voidless-generated assets, not uploads, and only specific source types/sizes. It also gives a worked workflow ('generate HD, then resize to 64 and to 32 for pixel versions') and contrasts with regenerating smaller. It stops short of naming sibling tools such as pixelate_image or generate_image as explicit alternatives, which would be the only thing separating this from a 5.

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

All Voidless toolsInspect
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