SpriteMCP

by NicoRMA

Overview Schema Source Related Servers Discussions Admin

Python

Local

clear_outfit_slot

Blank a specific outfit slot's design layer to transparent PNG and refresh its reference so the sprite updates.

Instructions

Blank one slot's design layer (transparent PNG) and refresh its reference.

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": {
      "name": "<name>",
      "slot": "<slot>"
    },
    "name": "clear_outfit_slot"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`slot`	Yes
`plan_id`	No
`output_dir`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 25, 2026

TDQS

C2.7/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral burden. It does disclose the main effect (blanking the design layer to a transparent PNG) and a secondary effect (refreshing its reference). However, it does not explain whether this is destructive to existing pixel data, what 'reference' means in the pipeline, or any ordering/constraints around the operation.

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?

The description is a single front-loaded sentence with no filler. Every phrase contributes: the action, the target layer format, and the reference refresh. It is concise, though it sacrifices some contextual detail that other dimensions need.

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?

For a mutating tool with four parameters, no annotations, and no parameter-level documentation in the description, this is incomplete. An agent cannot infer what 'name', 'plan_id', or 'output_dir' control, nor what 'refresh its reference' implies for the rest of the outfit pipeline. The output schema may describe returns, but the input behavior is under-specified.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not compensate. It never explains the required 'name' and 'slot' parameters, nor the optional 'plan_id' and 'output_dir'. The word 'slot' appears but merely echoes the schema property name, adding no semantic value beyond the JSON structure.

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 states a clear action ('Blank') applied to a specific resource ('one slot's design layer') and gives a concrete outcome ('transparent PNG' and refresh reference). It does not explicitly name sibling tools, but the reference to a slot's design layer distinguishes it from generic tools like clear_rect or clear_output_root.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives such as clear_rect, prepare_outfit_slot_reference, or fill_parts_on_slot. The description implies a use case—clearing a slot before reworking it—but does not state conditions, prerequisites, or exclusion criteria.

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