SpriteMCP

by NicoRMA

Overview Schema Source Related Servers Discussions Admin

Python

Local

paint_pixels

Paint individual pixels on a design layer by specifying coordinates and colors, updating the reference preview.

Instructions

Paint individual pixels onto design/layers/.png (REQUIRED paint path).

Each item: {x, y, color} where color is "#RRGGBB" / "#RRGGBBAA" / [r,g,b,a] / "transparent". Canvas coords match the character (body ref). Writes the design layer only; refreshes refs/_ref.png. Read preview_paths after. FORBIDDEN alternatives: Shell/PIL, GenerateImage.

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>",
      "pixels": "<pixels>"
    },
    "name": "paint_pixels"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`slot`	Yes
`scale`	No
`pixels`	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

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It discloses side effects ('Writes the design layer only; refreshes refs/<slot>_ref.png') and the follow-up action of reading preview_paths. It omits failure/error behavior and permission requirements, but it is transparent about mutation and scope.

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 compact and logically ordered: target path, item format, coordinate semantics, side effects, follow-up, and forbidden alternatives. Every sentence contributes information with no filler.

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

Completeness3/5

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

The description provides strong operational detail and the output schema covers return-value structure. However, given six parameters and zero schema description coverage, the unexplained required 'name' parameter and the relationship to sibling pixel tools leave an agent with non-trivial ambiguity.

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

Parameters2/5

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

Schema coverage is 0%, so the description is the only source of parameter meaning. It usefully explains the 'pixels' item structure and color formats, and implies 'slot' through the path, but it leaves the required 'name' parameter and the optional 'scale', 'plan_id', and 'output_dir' parameters unexplained.

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 specific verb ('Paint') and a precise target ('design/layers/<slot>.png') plus the required paint path, so the agent understands the primary action. It does not explicitly differentiate this tool from sibling pixel-editing tools like set_pixels or paint_from_commands, though the wording 'individual pixels' and 'design layer only' narrow the scope.

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?

It gives clear operational context: this is the designated pixel-painting path, it should be followed by reading preview_paths, and Shell/PIL and GenerateImage are explicitly forbidden alternatives. It does not explain when to choose this over closely related sibling tools such as set_pixels, fill_rect, or clear_rect.

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