Skip to main content
Glama
sloplink

aseprite-mcp

by sloplink
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Set pixels

aseprite_set_pixels

Sets individual pixels in Aseprite as a single undo step; use transparent black to erase. For larger changes, use the pixel map tool to reduce token usage.

Instructions

Sets individual pixels exactly, as a single undo step. The color '#00000000' erases a pixel. For more than a few pixels prefer aseprite_pixel_map (far fewer tokens).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameNoFrame number, 1-based (default: active frame)
layerNoLayer name (default: active layer)
pixelsYesList of [x, y, color]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.0
    • removedInput schema / properties / frame / maximum
      Removed value: -9007199254740991
    • changedInput schema / properties / frame / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / pixels / items / additionalItems
      Removed value: -false
    • changedInput schema / properties / pixels / items / items
      Previous value: -[
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "description": "Hex color: #rgb, #rgba, #rrggbb or #rrggbbaa",
-    "pattern": "^#?([0-9a-fA-F]{3}|[0-9a-fA-F]{4}|[0-9a-fA-F]{6}|[0-9a-fA-F]{8})$",
-    "type": "string"
-  }
-]New value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "description": "hex color",
+      "type": "string"
+    }
+  ]
+}
  2. First observedv0.2.0

TDQS

A4.4/5.0
Behavior3/5

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

With no annotations provided, the description must carry the burden for behavioral disclosure. It highlights two key behaviors: it sets pixels as a single undo step, and the special color '#00000000' erases a pixel. However, it does not disclose other potential behaviors such as how default frame/layer are handled beyond schema defaults, or any side effects on the active layer. The description adds some context beyond the schema but leaves room for more.

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 extremely concise, with two sentences that are packed with information. It front-loads the primary purpose, then immediately provides the critical detail about the erase color and the routing to aseprite_pixel_map. Zero wasted words; every sentence earns its place.

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

Completeness4/5

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

Given the tool's moderate complexity (3 parameters, all schema-covered) and no output schema, the description is quite complete. It covers the essential usage, the special erase case, and the alternative tool for scaling. The only minor gaps are that it doesn't explicitly state what happens if the layer or frame is invalid, or the exact behavior of the undo step (e.g., whether it groups all pixel sets into one undo). However, for most agent usage, it is sufficiently informative.

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?

The schema already documents 'pixels' as a list of [x, y, color] and describes frame and layer, so schema coverage is high at 100%. The description adds semantic value by explaining the special color for erasing, which is not in the schema, and clarifies the undo behavior. It does not describe the exact format of color beyond the schema's 'hex color' note, but the special case is valuable for correct usage.

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 clearly states the tool's function: setting individual pixels exactly as a single undo step. It distinguishes itself from the sibling aseprite_pixel_map by explicitly noting the token efficiency tradeoff, making it easy for an agent to choose between them.

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

Usage Guidelines5/5

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

It explicitly says when to use this tool vs the alternative: for more than a few pixels, prefer aseprite_pixel_map because it uses far fewer tokens. This gives clear guidance on when to use this tool (few pixels) and when not to, naming the sibling alternative directly.

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

Deploy Server

Other Tools