Skip to main content
Glama
sloplink

aseprite-mcp

by sloplink
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Clear

aseprite_clear

Clear a layer's contents in the active frame, or erase only a specified rectangular area to remove unwanted pixels.

Instructions

Clears the whole layer in the frame, or only a rectangle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rectNo[x, y, width, height] or "selection" (its bounding box)
frameNoFrame number, 1-based (default: active frame)
layerNoLayer name (default: active layer)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 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 / rect / additionalItems
      Removed value: -false
    • addedInput schema / properties / rect / anyOf
      Added value: +[
+  {
+    "items": {
+      "type": "number"
+    },
+    "maxItems": 4,
+    "minItems": 4,
+    "type": "array"
+  },
+  {
+    "enum": [
+      "selection"
+    ],
+    "type": "string"
+  }
+]
    • changedInput schema / properties / rect / description
      Previous value: -"[x, y, width, height]"New value: +"[x, y, width, height] or \"selection\" (its bounding box)"
    • removedInput schema / properties / rect / items
      Removed value: -[
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": 1,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": 1,
-    "type": "integer"
-  }
-]
    • removedInput schema / properties / rect / maxItems
      Removed value: -4
    • removedInput schema / properties / rect / minItems
      Removed value: -4
    • removedInput schema / properties / rect / type
      Removed value: -"array"
  2. First observedv0.2.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It fails to mention that the operation is destructive (clears pixel data), whether it is reversible, or whether it respects the current selection. It also does not clarify if the 'whole layer' means all frames or only the current frame, though the schema hints at frame specificity.

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 a single, concise sentence that efficiently conveys the core functionality. It is front-loaded with the primary action and clearly states the two modes, with no extraneous words or repetition.

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?

For a simple clear operation with three optional parameters and no output schema, the description is mostly adequate. However, it lacks important context such as the destructive nature of the operation, the default behavior when no rect is provided (which is implied but not explicit), and how frame and layer parameters interact. These gaps could lead to incorrect usage.

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?

The input schema already documents all three parameters with clear descriptions. The description adds a small hint that the 'rect' parameter is for clearing a rectangle and that the default is the whole layer, but it does not introduce any new semantic meaning beyond what the schema provides. Since schema coverage is 100%, a baseline score of 3 is appropriate.

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: it clears a whole layer or a rectangular region. The verb 'clears' and the resource 'layer' are specific, and it distinguishes the two modes of operation. This unambiguously separates it from sibling tools like draw, copy, or set_pixels.

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?

No guidance is given on when to use this tool versus alternatives. The description does not mention any prerequisites, exclusions, or conditions for use. It merely states what it does, leaving the agent to infer that it is the appropriate tool for clearing operations.

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