Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

flatten_sprite

Destructive

Flatten all layers in an Aseprite sprite into a single layer to simplify the file before export or further editing.

Instructions

Flatten all layers into a single layer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flatten_sprite"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotation already declares destructiveHint=true; the description adds nothing about what is actually lost (layer names, ordering, per-layer edits), that the merge is irreversible, or whether the optional `file` target is modified in place. It restates the operation rather than disclosing its consequences.

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?

One short, front-loaded sentence with no filler. Brevity is appropriate, though it is brevity at the cost of the missing scope and target information.

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?

This is a destructive, one-parameter mutation with no output schema and no documented parameter semantics, so the description should carry most of the burden and does not. An agent cannot determine the target sprite, whether the change is saved to disk, or whether it is recoverable.

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?

The single parameter `file` has 0% schema description coverage and is never mentioned in the description, so its meaning (which sprite/document is flattened when omitted, and whether null means the active sprite) is left entirely unexplained. The description provides no compensation for the coverage gap.

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?

The description states a specific verb and effect ('Flatten all layers into a single layer'), so an agent can tell it merges layers rather than adding or reordering them. It does not name the sprite it operates on (active sprite vs. the `file` argument) or distinguish itself from neighboring layer tools, which keeps it from 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 Guidelines3/5

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

Usage is only implied: an agent can infer this is for collapsing a layered sprite, but there is no statement of when to prefer it over save/export, no precondition (e.g., sprite must be open), and no exclusion for cases where layers should be preserved.

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