Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

delete_layer

Destructive

Removes a layer by name from an Aseprite file or the active document, enabling targeted cleanup of artwork.

Instructions

Delete the layer with the given name.

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

Input Schema

NameRequiredDescriptionDefault
fileNo
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/5.0
Behavior2/5

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

The destructiveHint=true annotation already carries the safety signal, so the description needs to add context such as whether the deletion is reversible, whether layer contents are lost permanently, or whether the currently selected layer changes. It adds none of this; "Delete" merely restates the annotation.

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 or redundancy. It is efficiently written, though its brevity is a consequence of omitting information rather than of tight editing.

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 destructive mutation with no output schema and zero parameter documentation, the description should say more about irreversibility, scope (which file), and failure modes such as a nonexistent layer name. As written it is too thin for the tool's risk profile.

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% across two parameters. The description only clarifies that `name` identifies the target layer; the `file` parameter (which presumably scopes the document) is left entirely unexplained in both schema and description, so the description fails to compensate 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 resource ("Delete the layer") plus the identifier used to target it, which distinguishes it from siblings like delete_frame, delete_slice, and delete_tag by resource type. It is not tautological, but it stops short of any qualifier that would separate it from layer-level operations such as merge_layer_down.

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 mention of prerequisites (e.g., can the last layer be deleted, must it be selected first), and no reference to alternatives such as merge_layer_down when the intent is to remove content while preserving pixels. The agent must infer all usage conditions.

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