Aseprite MCP

Overview Schema Source Related Servers Discussions Admin

create_character_sprite

Scaffold a character sprite project with a transparent canvas, layered body/details, an auto-generated shading palette from a base color, and an optional outlined placeholder to draw over.

Instructions

Scaffold a character sprite project: a transparent canvas with a tidy layer stack (body + details), an auto-generated shading palette ramp from base_color, and (optionally) an outlined placeholder body to draw over.

Returns a ``workflow_manifest.v1`` manifest (sprite summary, created files,
palette, and suggested next actions), plus `pixels_written` for the placeholder it
drew. With `with_placeholder=False` nothing is drawn and the field is absent.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`width`	No	Default: 32.
`height`	No	Default: 32.
`base_color`	No	Default: "#3878c8".	#3878c8
`with_placeholder`	No	Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.10.0Oct 4, 2026
- addedInput schema / properties / base_color / description
```
Added value: +"Default: \"#3878c8\"."
```
- removedInput schema / properties / base_color / title
```
Removed value: -"Base Color"
```
- addedInput schema / properties / height / description
```
Added value: +"Default: 32."
```
- removedInput schema / properties / height / title
```
Removed value: -"Height"
```
- removedInput schema / properties / name / title
```
Removed value: -"Name"
```
- addedInput schema / properties / width / description
```
Added value: +"Default: 32."
```
- removedInput schema / properties / width / title
```
Removed value: -"Width"
```
- addedInput schema / properties / with_placeholder / description
```
Added value: +"Default: true."
```
- removedInput schema / properties / with_placeholder / title
```
Removed value: -"With Placeholder"
```
- removedInput schema / title
```
Removed value: -"create_character_spriteArguments"
```
First observedv0.7.0Jul 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false. The description adds real context beyond that: it lists the created files, describes the auto-generated palette ramp, and specifies the conditional behavior of with_placeholder=False (nothing drawn, pixels_written absent). It stops short of noting overwrite/collision or permission requirements for a write tool.

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?

Front-loaded with the primary action and artifact list, then a second paragraph on the return contract. Both sentences carry weight; nothing is padded, though the return detail could be tightened.

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?

With no output schema, the description rightly covers the workflow_manifest.v1 return and the conditional pixels_written field. Combined with the artifact enumeration, an agent has what it needs to call this correctly; only edge cases like existing-name conflicts are unaddressed.

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 80%, so most params are self-documented and the baseline would be 3. The description earns above baseline by explaining what base_color actually drives (an auto-generated shading ramp) and the effect of with_placeholder, meaning not captured in the schema. name/width/height remain unelaborated in the text.

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 and resource ('scaffold a character sprite project') and enumerates the concrete artifacts produced: transparent canvas, body+details layer stack, palette ramp, optional placeholder. The agent can distinguish it from the generic 'create_sprite' sibling by the scaffolding behavior, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the scaffolding framing and the with_placeholder toggle, but there is no explicit when-to-use/when-not guidance nor any pointer to alternatives like create_sprite or create_icon_set. The agent must infer that this is a project-start helper.

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

Deploy Server