Retro Diffusion Pixel Art MCP

Estimate Edit Cost (Free)

estimate_edit_tool_cost

Read-onlyIdempotent

Validate an edit-tool request and estimate its cost and duration without running it. Always free.

Input Schema

TableJSON Schema

Name	Required	Description
`width`	No	k_centroid_downscale: target width in pixels (required for that tool).
`height`	No	k_centroid_downscale: target height in pixels (required for that tool).
`prompt`	No	What to generate or change (required by image_edit and inpainting; optional for outpainting).
`tile_x`	No	seam_tiling: repair the horizontal seam (tool default applies when omitted).
`tile_y`	No	seam_tiling: repair the vertical seam (tool default applies when omitted).
`tool_id`	Yes	Edit tool id. One of: image_edit, inpainting, outpainting, seam_tiling, background_remover, color_style_transfer, color_reducer, palette_converter, pixel_correction, k_centroid_downscale, rotate. Use list_edit_tools for authoritative fields, costs, and limits.
`expand_top`	No	Outpainting: pixels to add on the top edge.
`mask_image`	No	Base64 mask for inpainting: white pixels are regenerated, black pixels are kept.
`rd_api_key`	No	RetroDiffusion API key (rdpk-...) for this call only; overrides session or header auth.
`seam_width`	No	seam_tiling: width in pixels of the seam band to repair.
`color_count`	No	color_reducer: target number of colors.
`dither_mode`	No	color_reducer/palette_converter: dithering mode.
`expand_left`	No	Outpainting: pixels to add on the left edge.
`input_image`	Yes	Base64 PNG of the image to edit (raw base64 or a data URL). Required by every edit tool.
`expand_right`	No	Outpainting: pixels to add on the right edge.
`soft_inpaint`	No	Inpainting/outpainting: blend edits softly with the surrounding pixels.
`expand_bottom`	No	Outpainting: pixels to add on the bottom edge.
`input_palette`	No	Base64 image of a color palette; output colors are constrained to it.
`dither_strength`	No	color_reducer/palette_converter: dithering strength, 0-10 (0 disables, default 5).
`timeout_seconds`	No	Read-timeout override in seconds for this call; increase for animations or large batches.
`rotation_degrees`	No	rotate: rotation angle in degrees (clean-edge pixel rotation).
`extra_input_image`	No	Second base64 input image for styles that use one (e.g. the second texture in rd_tile__tileset_advanced).
`force_solid_pixels`	No	background_remover: force fully solid or fully transparent pixels (tool default applies when omitted).
`repair_window_size`	No	seam_tiling: size of the repair window.
`transparency_threshold`	No	background_remover: alpha threshold for treating pixels as transparent.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 17, 2026

changedInput schema / properties / dither_strength / description

Previous value: -"color_reducer/palette_converter: dithering strength."New value: +"color_reducer/palette_converter: dithering strength, 0-10 (0 disables, default 5)."

AddedJul 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already mark readOnlyHint, idempotentHint, destructiveHint as false. The description adds 'Always free' and 'without running it,' which goes beyond annotations and provides useful cost transparency.

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?

Two concise sentences that pack key info: purpose, cost, and behavior. Efficient and front-loaded.

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?

Given 25 parameters with 100% schema coverage and annotations, the description captures the core function well. The 'Always free' note is valuable. Could mention when to use over run_edit_tool explicitly.

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

Parameters3/5

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

Schema coverage is 100% with detailed descriptions for each parameter. The description adds 'Always free' but no extra parameter info. Baseline 3 is appropriate.

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 clearly states 'validate an edit-tool request and estimate its cost and duration' and notes 'Always free,' distinguishing it from run_edit_tool.

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?

Explicitly says this is for validation and estimation without running, implying use before executing. No direct sibling alternative named, but context with run_edit_tool is implied.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?