Retro Diffusion Pixel Art MCP

Estimate Low-Poly Job

estimate_lowpoly_cost

Read-onlyIdempotent

Price a Low-Poly job without starting it (free). For generate with size auto, returns the size auto would pick. style prices a generate in that style (Lite styles cost less); other operations use the model's own style.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`size`	No	Cube size in texels: "16", "32", "64", "128", "256", or "auto" (default). Auto reads the prompt; reference-image-only requests default to 64. Bigger sizes cost more (see get_lowpoly_pricing).
`style`	No	Low-Poly style id: rd_lowpoly__detailed (default, free-form shapes), rd_lowpoly__blocky (boxes only, tilted where needed, Minecraft-like), their Lite versions rd_lowpoly__detailed_lite / rd_lowpoly__blocky_lite (a lighter model: simpler results for much less, and Lite prices for everything done to the model later), or another style listed by get_lowpoly_pricing (each style lists its prices).
`prompt`	No	What to build or change, up to 250 characters.
`asset_id`	No	Required for revise, animate, split and rerig.
`operation`	No	generate, revise, animate, split or rerig.	generate
`rd_api_key`	No	RetroDiffusion API key (rdpk-...) for this call only; overrides session or header auth.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

addedInput schema / properties / style

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Low-Poly style id: rd_lowpoly__detailed (default, free-form shapes), rd_lowpoly__blocky (boxes only, tilted where needed, Minecraft-like), their Lite versions rd_lowpoly__detailed_lite / rd_lowpoly__blocky_lite (a lighter model: simpler results for much less, and Lite prices for everything done to the model later), or another style listed by get_lowpoly_pricing (each style lists its prices)."
+}

Changed2 schema fields changedSep 25, 2026

changedInput schema / properties / asset_id / description

Previous value: -"Required for revise, animate and split."New value: +"Required for revise, animate, split and rerig."

changedInput schema / properties / operation / description

Previous value: -"generate, revise, animate or split."New value: +"generate, revise, animate, split or rerig."

Changed2 schema fields changedSep 25, 2026

changedInput schema / properties / asset_id / description

Previous value: -"Required for revise and animate."New value: +"Required for revise, animate and split."

changedInput schema / properties / operation / description

Previous value: -"generate, revise or animate."New value: +"generate, revise, animate or split."

AddedSep 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already mark this as read-only and idempotent, and the description reinforces that by stating it does not start the job and is free. It adds valuable behavioral nuance beyond annotations: auto size returns the size that would be picked, and style only affects pricing for generate while other operations use the model's own style.

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?

Three short sentences, with the core purpose front-loaded and no filler. Each sentence contributes either a primary function, a size edge case, or a style/pricing interaction.

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 read-only estimator with a rich schema, an output schema, and annotations covering safety, the description covers the non-obvious behaviors an agent needs: no execution, no charge, auto-size behavior, and style/operation pricing interaction. Remaining operation and asset_id details are already in the 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?

The input schema already documents all six parameters at 100% coverage, so the baseline is 3. The description adds non-obvious semantic detail: size=auto causes the estimate to reveal the auto-selected size, and style affects only generate pricing, with Lite styles costing less and other operations ignoring style. This is meaningful added value.

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 opens with a specific verb and resource: 'Price a Low-Poly job' without starting it, clearly distinguishing this from start_lowpoly_* tools. It also highlights the special auto-size behavior for generate, differentiating the tool's purpose from generic pricing-list endpoints like get_lowpoly_pricing.

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 phrase 'without starting it (free)' gives clear context: use this to estimate cost before committing to a job, not to execute one. It does not explicitly name alternatives or exclusion cases, but the context is enough to route an agent away from the start_lowpoly_* siblings.

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

All Retro Diffusion Pixel Art MCP 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?