Retro Diffusion Pixel Art MCP

Check Async Job

get_inference_job

Read-onlyIdempotent

Check the status of an async generation started with start_inference_job.

Statuses: pending, running, succeeded, failed. On success the result carries hosted output_urls (raw base64 payloads are excluded to keep MCP outputs compact).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`task_id`	Yes	Async job id returned by start_inference_job.
`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

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already provide readOnlyHint and idempotentHint. Description adds valuable context about output_urls and omission of base64 payloads, enhancing transparency.

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?

Two sentences, front-loaded with purpose, no fluff. Every sentence adds value.

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 output schema exists, description covers statuses and output details adequately. No gaps for this simple tool.

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%, and description adds helpful context for task_id (links to start_inference_job). Slight added value beyond schema.

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?

Description clearly states it checks async job status, using specific verb and resource. Distinguishes from sibling tools like start_inference_job and list_inference_jobs.

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 links to start_inference_job and mentions statuses, but could more explicitly differentiate from list_inference_jobs for batch queries.

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.

Most tools have clearly distinct purposes (e.g., create_inference vs start_inference_job vs get_inference_result). However, the difference between create_user_style/update_user_style and per-inference references could still cause confusion, and list_available_models/list_available_styles overlap slightly.

Naming Consistency5/5

All tool names consistently follow a verb_noun pattern (e.g., create_inference, get_balance, list_edit_tools, delete_user_style). No mixing of camelCase or other styles, making the surface highly predictable.

Tool Count5/5

With 20 tools covering authentication, inference (sync/async), styles, editing, cost estimation, and status, the count is appropriate for a pixel art generation API. Each tool addresses a distinct need without bloat.

Completeness4/5

The tool set covers the full lifecycle: auth, cost estimation, synchronous/async generation, style management, editing, and result retrieval. A minor gap is the lack of a tool to list or manage user styles (e.g., get_user_styles), but this is non-critical for core workflows.

Resources

Need Help?