Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

delete_slice

Destructive

Deletes a named slice from an Aseprite sprite in one undo step, with an optional headless file target, so you can clean up export regions without manual editing.

Instructions

Delete the slice with the given name. 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": {
      "name": "<name>"
    },
    "name": "delete_slice"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

The destructiveHint=true annotation already signals a destructive write, so the description's added value is the 'One undo step' statement, which usefully tells the agent the deletion is reversible via a single undo. It does not say what happens if the named slice is absent or whether child data (pivots, centers) is removed with it.

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?

Three short front-loaded fragments, each carrying distinct information (action, reversibility, headless requirement). No filler, though the sentence-fragment style is slightly terse and the headless note reads as an afterthought.

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 simple two-parameter destructive tool with an annotation covering the safety profile and no output schema, the description covers the essentials: what is deleted, how it is identified, recoverability, and headless mode. Missing are error behavior for a nonexistent slice and any note about side effects on related data.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 carry parameter meaning. It covers both parameters at a minimal level: `name` identifies the slice to delete, and `file` is only needed in headless mode. It adds no format, path, or naming-convention detail beyond that, leaving gaps in a 0%-coverage schema.

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 slice') and clarifies that the slice is identified by name, which matches the required parameter. It does not differentiate itself from sibling deleters like delete_frame or delete_layer, but the resource noun makes the target 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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as undo or create_slice. The only contextual cue is 'Headless: pass ``file``', which addresses execution mode rather than tool selection.

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