Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

merge_layer_down

Destructive

Merge a layer into the layer directly beneath it to flatten stacked artwork and simplify layer editing in Aseprite.

Instructions

Merge a layer into the layer directly beneath it.

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": "merge_layer_down"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.8/5.0
Behavior2/5

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

The destructiveHint annotation already flags this as a destructive operation, and the description adds only that the target is the layer directly beneath. It does not say that the named layer is consumed, which layer's name/blend mode/opacity survives, whether the merge is undoable, or how locked/hidden layers are treated — significant gaps for a destructive mutation.

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?

A single front-loaded sentence with no filler. Its terseness is a function of missing content rather than bloat, but the sentence itself is well-formed and efficient.

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 destructive, two-parameter mutation with no output schema and zero schema documentation, the definition is thin: it omits parameter meaning, merge-result behavior, and failure conditions. An agent could invoke it but might target the wrong file or expect the wrong layer to survive.

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 two parameters, so the description must compensate and does not. 'Name' is only implicitly the layer to merge, and the 'file' parameter (default null) is never mentioned, leaving it unclear which document or file the operation applies to.

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 (merge) and resource (layer) plus the direction of the merge ('down'), which is more than a restatement of the name. It does not differentiate from any sibling, but among the listed siblings none perform a merge, so the operation is reasonably unambiguous.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or conditions (e.g., what happens at the bottom of the stack, whether a selection is required). The agent must infer usage entirely from the tool name.

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