Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

import_image_as_layer

Imports an external PNG or image file into a new Aseprite layer at a chosen X/Y position, creating a reference or trace layer for concept-art intake in one undoable step.

Instructions

Import an external image file (PNG, etc.) into a new layer at (x, y) — a reference/trace layer for concept-art intake. One undo step. Headless: pass file.

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": {
      "image_path": "<image_path>"
    },
    "name": "import_image_as_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
fileNo
image_pathYes
layer_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior3/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 burden. It usefully discloses that the action is a single undo step (reversibility) and that headless callers should use 'file' rather than the required 'image_path'. It does not state what happens on a bad path, whether an existing layer is overwritten, or what the call returns.

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?

The definition is compact and front-loaded: the verb, resource, and coordinate semantics come first, followed by purpose and two short operational notes. The trailing 'Headless: pass ``file``' fragment is slightly clipped but earns its space.

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?

With five parameters at 0% schema coverage, no output schema, and annotations limited to a title, the description should do more. Unexplained layer_name and the redundant-looking image_path/file pair leave an agent guessing how to construct a valid call.

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%, so the description must explain all five parameters. It clarifies x, y placement and partially signals the two path parameters via 'Headless: pass file', but it never explains layer_name and, more importantly, leaves the image_path-versus-file relationship ambiguous for a tool where one is required and the other optional.

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 gives a specific verb and resource ('Import an external image file into a new layer') plus the intended use ('a reference/trace layer for concept-art intake'), which is far more than the bare title. It does not name or distinguish itself from plausible siblings such as add_reference_image or import_spritesheet, so an agent must infer the boundary between them.

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?

'For concept-art intake' and 'Headless: pass file' imply the contexts where this tool applies, and the headless note is a real operational hint. However, there is no explicit when-to-use versus when-not guidance, and nothing tells the agent when to prefer add_reference_image or import_spritesheet over this.

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