Retro Diffusion Pixel Art MCP

Get Style Usage

get_style_usage

Read-onlyIdempotent

Explain how to use a public prompt_style from the RetroDiffusion API.

Use this before create_inference if you are unsure whether a style expects input_image, supports per-inference reference_images, or whether you meant style-level style_reference_images.

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": {
      "prompt_style": "<prompt_style>"
    },
    "name": "get_style_usage"
  }
}

Input Schema

Name	Required	Description	Default
`rd_api_key`	No	RetroDiffusion API key (rdpk-...) for this call only; overrides session or header auth.
`prompt_style`	Yes	Style id from list_available_styles (e.g. 'rd_core__default', 'rd_pro__isometric', or a custom 'user__...' style).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 11, 2026

changedInput schema / properties / prompt_style / description

Previous value: -"Style id from list_available_styles (e.g. 'rd_fast__default', 'rd_pro__isometric', or a custom 'user__...' style)."New value: +"Style id from list_available_styles (e.g. 'rd_core__default', 'rd_pro__isometric', or a custom 'user__...' style)."

Changed2 schema fields changedJul 10, 2026

addedInput schema / properties / prompt_style / description

Added value: +"Style id from list_available_styles (e.g. 'rd_fast__default', 'rd_pro__isometric', or a custom 'user__...' style)."

addedInput schema / properties / rd_api_key / description

Added value: +"RetroDiffusion API key (rdpk-...) for this call only; overrides session or header auth."

First observedJul 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that this is an explanatory lookup that helps resolve style-expectation ambiguity before inference, though it does not discuss auth, rate limits, or response behavior beyond what the schema and output schema provide.

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 two sentences and front-loads the core purpose before the usage guidance. Every sentence contributes useful selection context, with no repetition or filler.

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?

Given the low complexity of two parameters and a 100% covered schema, plus an output schema and rich annotations, the description supplies the missing selection context. An agent knows what the tool does and when to call it before inference, and return values are handled by the output schema.

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 description coverage is 100%, so both parameters are already documented by the input schema. The description mentions 'public prompt_style' and the concepts of input_image, reference_images, and style_reference_images, but it does not add syntax, format, or validation detail beyond what the schema already provides.

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 states a specific verb and resource: 'Explain how to use a public prompt_style'. It also distinguishes the tool from create_inference by positioning it as a pre-inference usage check, so an agent can tell what this tool is for 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?

The description gives clear usage context: call it before create_inference when unsure about a style's input_image, reference_images, or style_reference_images expectations. It lacks explicit when-not-to-use guidance or an alternative such as list_available_styles, so it falls short of the full 5.

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?