Aseprite MCP

Overview Schema Source Related Servers Discussions Admin

create_rpg_item_sheet

Scaffold an RPG item sheet grid with one named slice per item and placeholder art, returning a manifest for sprite workflows.

Instructions

Scaffold an RPG item sheet: a grid sheet with one named slice per item (default sword/shield/potion/coin/key/gem), each with a placeholder.

Returns a ``workflow_manifest.v1`` manifest (kind "rpg_item_sheet"); item regions
appear as slices (named after each item) under `sprite.slices`.

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_rpg_item_sheet"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`items`	No
`columns`	No
`item_size`	No	Default: 16.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv0.10.0Oct 4, 2026
- removedInput schema / properties / columns / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / columns / default
```
Removed value: -null
```
- removedInput schema / properties / columns / title
```
Removed value: -"Columns"
```
- addedInput schema / properties / columns / type
```
Added value: +"integer"
```
- addedInput schema / properties / item_size / description
```
Added value: +"Default: 16."
```
- removedInput schema / properties / item_size / title
```
Removed value: -"Item Size"
```
- removedInput schema / properties / items / anyOf
```
Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / items / default
```
Removed value: -null
```
- addedInput schema / properties / items / items
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / items / title
```
Removed value: -"Items"
```
- addedInput schema / properties / items / type
```
Added value: +"array"
```
- removedInput schema / properties / name / title
```
Removed value: -"Name"
```
- removedInput schema / title
```
Removed value: -"create_rpg_item_sheetArguments"
```
First observedv0.7.0Jul 29, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already indicate this is not read-only and not open-world. The description adds some behavioral context by disclosing the return manifest kind and slice structure, but it does not say whether it overwrites existing data, what permissions are needed, or what side effects occur.

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?

Two compact, front-loaded sections: what it scaffolds first, then return details. Every sentence earns its place, with no redundant or filler text.

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 composite creation tool with low schema coverage and no output schema, the description covers purpose and return format adequately. However, it omits parameter explanations, side effects, prerequisites, and usage context, leaving meaningful gaps.

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 description coverage is only 25%, so the description must compensate. It partly explains the items parameter via default item names and the slice mapping, but does not explain name or columns, and item_size is only documented in the schema with a default.

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 ("Scaffold") and resource ("RPG item sheet"), and describes the output: a grid sheet with one named slice per item and default items. It is clear but does not explicitly distinguish itself from sibling creation tools like create_sprite or create_character_sprite.

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?

Gives no when-to-use guidance, no prerequisites, and no alternatives. The purpose implies a scaffolding scenario, but there is no explicit instruction about when to choose this over other creation tools.

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

Deploy Server