Skip to main content
Glama
Sign In
Aseprite MCP

Aseprite MCP

by MalloyTheDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

convert_layer_to_background

Convert a normal layer into the sprite's opaque Background layer to make it the base for compositing.

Instructions

Convert a normal layer into the sprite's opaque Background layer.

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": {
      "filename": "<filename>",
      "layer": "<layer>"
    },
    "name": "convert_layer_to_background"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerYes
filenameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.10.0
    • removedInput schema / properties / filename / title
      Removed value: -"Filename"
    • removedInput schema / properties / layer / title
      Removed value: -"Layer"
    • removedInput schema / title
      Removed value: -"convert_layer_to_backgroundArguments"
  2. First observedv0.7.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, which tell the agent this mutates state; the description adds that the resulting layer is opaque but says nothing about whether the original layer is replaced, what happens to an existing background layer, or whether the operation is reversible. No destructiveHint is declared and the description does not compensate.

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?

A single tight sentence with no wasted words, front-loading the verb and the target resource.

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

Completeness2/5

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

For a mutating, non-read-only tool with no output schema and undocumented parameters, the description should state preconditions (e.g., only one background layer allowed) and the effect on existing content. None of that is present, leaving the definition inadequate for its complexity.

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 0% for both required parameters (filename, layer), and the description never mentions them. It does not clarify how the layer is identified (name vs. index) or what filename refers to, so the agent must guess at parameter semantics.

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?

Names a specific verb (convert) and resource (a normal layer) and states the transformation target (the sprite's opaque Background layer). It is distinguishable in intent, though it does not explicitly name the reverse sibling convert_background_to_layer, so it stops short of a 5.

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 gives no when-to-use or when-not-to-use guidance, and does not mention the natural alternative convert_background_to_layer. An agent must infer the correct context from the name alone.

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