Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

add_layer

Add a new empty layer at the top of the Aseprite layer stack, optionally with a custom name, to organize and build up pixel-art compositions.

Instructions

Add a new empty layer (optionally named) at the top of the stack.

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

Input Schema

NameRequiredDescriptionDefault
fileNo
nameNo

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?

Annotations carry only a title, so the description bears the full behavioral burden. It does disclose the key side effect that the layer lands at the top of the stack, but says nothing about whether the new layer becomes selected, whether the operation is undoable, or what a 'layer' contains by default.

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 sentence, front-loaded with the verb and resource, with no filler. It is terse to the point of omitting needed detail rather than being verbose, but nothing in it is wasted.

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 two-parameter mutation with no annotations and no output schema, the definition leaves the 'file' parameter unexplained and omits selection/undo behavior. The description is not sufficient on its own for an agent to call this confidently in ambiguous cases.

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, so the description must compensate. It covers 'name' via 'optionally named', but the 'file' parameter is never mentioned and its meaning on an 'add empty layer' operation is genuinely unclear.

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 and resource ('Add a new empty layer') plus the resulting placement ('at the top of the stack'), which tells an agent what the operation produces. It does not name or distinguish itself from plausible siblings such as create_tilemap_layer or import_image_as_layer, so differentiation is left implicit.

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 and no mention of alternatives. An agent must infer from the word 'empty' alone that this is not the tool for importing an image or creating a tilemap-backed layer.

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