Skip to main content
Glama
Sign In

Retro Diffusion Pixel Art

by ai.retrodiffusion
OverviewDiscussionsAdmin

Delete Custom Style

delete_user_style
DestructiveIdempotent

Delete a user style using /v2/styles/{style_id}. style_id can be either internal id or prompt_style/public_id.

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": {
      "style_id": "<style_id>"
    },
    "name": "delete_user_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
style_idYesStyle id — the internal id or the prompt_style/public id (e.g. user__mystyle_ab12).
rd_api_keyNoRetroDiffusion API key (rdpk-...) for this call only; overrides session or header auth.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior1/5

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

The description says 'Delete a user style,' which is a destructive mutation, while the annotations declare readOnlyHint: true. This directly contradicts the operation's semantics, so the score must be 1 per the rubric. The description adds no mitigating context about irreversibility or side effects.

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 short, front-loaded sentences with no filler: the first states the action and endpoint, the second clarifies the accepted id forms. This is appropriately sized for a simple delete operation.

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

Completeness2/5

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

Although an output schema exists and the operation is simple, the readOnlyHint contradiction leaves the behavior ambiguous. The description also does not address ownership/permissions, irreversibility of deletion, or behavior when style_id is not found, so it is not complete enough for a destructive tool carrying conflicting annotations.

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 style_id and rd_api_key are already documented. The description repeats the fact that style_id can be an internal id or prompt_style/public id, matching the schema description without adding new information. It meets the baseline but does not go beyond it.

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: 'Delete a user style' and identifies the exact endpoint /v2/styles/{style_id}. This clearly distinguishes the tool from siblings such as create_user_style and update_user_style without being a tautology.

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 intended use is plainly stated: use this when a user style should be removed. It gives clear context, but it does not explicitly name alternatives or exclusions, such as using update_user_style when only a modification is needed.

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 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