Skip to main content
Glama
Sign In
Aseprite MCP Tools

Aseprite MCP Tools

by ZeroTian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

flatten_sprite

Combine all layers of an Aseprite file into one single layer, simplifying the sprite structure.

Instructions

Flatten all layers into a single layer.

Args: filename: Aseprite file to modify

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

Input Schema

NameRequiredDescriptionDefault
filenameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so description must bear full burden. It does not disclose whether the operation is destructive, reversible, or what happens to layer properties like blend modes or opacity. Minimal behavioral context.

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?

Two sentences are very concise, but the second sentence could be integrated into the first. No wasted words, but the structure could be more streamlined.

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?

Given the tool's simplicity (single parameter, no output schema), the description is adequate but lacks details on the result (e.g., new layer name, changes to sprite structure). It meets minimum viability.

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?

Schema coverage is 0% for filename, but the description adds 'Aseprite file to modify', specifying the file type and action. This adds some meaning beyond the parameter name, though limited.

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 uses a specific verb 'Flatten' and resource 'layers into a single layer', clearly stating the action. It distinguishes from sibling tools like merge_layer_down which only merges one layer down, not all layers.

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 on when to use this tool versus alternatives like merge_layer_down or other layer operations. No explicit context for usage or exclusions.

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