Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

clear_cel

Destructive

Clears pixel content from a specified layer and frame by making the cel fully transparent, preparing that animation cell for new artwork.

Instructions

Empty the cel at the given layer + frame (transparent).

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

Input Schema

NameRequiredDescriptionDefault
fileNo
frameNo
layerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, and the description usefully clarifies the destructive action's nature by specifying the result is transparency rather than deletion. It does not disclose whether the operation is undoable, what happens if the cel is already empty, or how omitted layer/frame/file resolve to the current context — relevant because all three params default to null.

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, and the '(transparent)' qualifier is placed where it matters. The brevity is efficient rather than padded, though it borders on under-specification.

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 annotations beyond destructiveHint, no output schema, and 0% schema coverage on three optional parameters, the description should say how defaults are resolved and what the caller gets back. It covers only two of the three parameters and none of the defaulting behavior.

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% and all three parameters are optional nullable values, so the description must compensate. It only references layer and frame, leaving the file parameter and the default-resolution behavior (current file/layer/frame) entirely undocumented.

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 (empty) plus the resource (the cel) and the targeted coordinates (layer + frame), and adds the result '(transparent)' so the agent knows it is not a delete. It does not name or contrast any sibling such as set_cel_opacity, so it falls short of the 5 bar.

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 explicit when-to-use, when-not-to-use, or alternative such as setting opacity to zero. The use case is only implied by the verb 'empty'.

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