Aseprite MCP

Overview Schema Source Related Servers Discussions Admin

stamp_pattern

Fill a region with a repeating pattern by tiling a source image or sprite, with optional spacing, opacity, and blend mode.

Instructions

Tile an image/sprite across a region to fill it with a repeating pattern.

Args:
    source: Image/sprite to tile.
    x, y, width, height: Region to fill (defaults to the whole canvas).
    spacing_x, spacing_y: Gap between tiles.
    opacity, blend_mode: Compositing of each tile.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`x`	No	Default: 0.
`y`	No	Default: 0.
`frame`	No	Default: 1.
`layer`	No
`width`	No
`height`	No
`source`	Yes
`opacity`	No	Default: 255.
`filename`	Yes
`spacing_x`	No	Default: 0.
`spacing_y`	No	Default: 0.
`blend_mode`	No	Default: "normal".	normal

Schema Changelog

Changes observed during successful MCP inspections.

Changed29 schema fields changedv0.10.0Oct 4, 2026
- addedInput schema / properties / blend_mode / description
```
Added value: +"Default: \"normal\"."
```
- removedInput schema / properties / blend_mode / title
```
Removed value: -"Blend Mode"
```
- removedInput schema / properties / filename / title
```
Removed value: -"Filename"
```
- addedInput schema / properties / frame / description
```
Added value: +"Default: 1."
```
- removedInput schema / properties / frame / title
```
Removed value: -"Frame"
```
- removedInput schema / properties / height / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / height / default
```
Removed value: -null
```
- removedInput schema / properties / height / title
```
Removed value: -"Height"
```
- addedInput schema / properties / height / type
```
Added value: +"integer"
```
- removedInput schema / properties / layer / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / layer / default
```
Removed value: -null
```
- removedInput schema / properties / layer / title
```
Removed value: -"Layer"
```
- addedInput schema / properties / layer / type
```
Added value: +"string"
```
- addedInput schema / properties / opacity / description
```
Added value: +"Default: 255."
```
- removedInput schema / properties / opacity / title
```
Removed value: -"Opacity"
```
- removedInput schema / properties / source / title
```
Removed value: -"Source"
```
- addedInput schema / properties / spacing_x / description
```
Added value: +"Default: 0."
```
- removedInput schema / properties / spacing_x / title
```
Removed value: -"Spacing X"
```
- addedInput schema / properties / spacing_y / description
```
Added value: +"Default: 0."
```
- removedInput schema / properties / spacing_y / title
```
Removed value: -"Spacing Y"
```
- removedInput schema / properties / width / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / width / default
```
Removed value: -null
```
- removedInput schema / properties / width / title
```
Removed value: -"Width"
```
- addedInput schema / properties / width / type
```
Added value: +"integer"
```
- addedInput schema / properties / x / description
```
Added value: +"Default: 0."
```
- removedInput schema / properties / x / title
```
Removed value: -"X"
```
- addedInput schema / properties / y / description
```
Added value: +"Default: 0."
```
- removedInput schema / properties / y / title
```
Removed value: -"Y"
```
- removedInput schema / title
```
Removed value: -"stamp_patternArguments"
```
First observedv0.7.0Jul 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations only supply readOnlyHint=false and openWorldHint=false. The description does not disclose that existing pixels in the region are overwritten, that it operates on a specific file/layer/frame context (three params it never mentions), or how compositing accumulations behave. It adds little beyond the write hint.

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?

Purpose sentence is front-loaded and the arg list is compact with no wasted prose. Structure is clean, though the args block reads more like a schema echo than value-adding guidance.

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 12-param mutation tool with no output schema, the description covers most parameters and the core behavior, but leaves the file/layer/frame targeting context and the overwrite semantics unaddressed. Adequate but with clear gaps.

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?

Schema coverage is 58% and much of it is trivial ('Default: 0.'), so the description carries real weight here: it explains source, the region defaults, spacing, and per-tile opacity/blend. It still omits filename, layer, and frame, which are inferred rather than explained.

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?

States a specific verb ('tile') and resource ('image/sprite'), and clarifies the result ('fill it with a repeating pattern'). This broadly distinguishes it from stamp_file, but it never explicitly contrasts the two (single vs repeating stamp), so differentiation relies on inference.

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?

The description lists arguments but gives no when-to-use guidance, no when-not-to-use conditions, and no pointer to alternatives like stamp_file, fill_area, or fill_checkerboard. An agent must guess which fill/tiling sibling to pick.

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

Deploy Server

stamp_pattern

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools