remove_slice
Delete a slice by name from an Aseprite sprite, using the filename to locate the file and the slice name to remove it.
Instructions
Delete a slice by name.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| filename | Yes |
Delete a slice by name from an Aseprite sprite, using the filename to locate the file and the slice name to remove it.
Delete a slice by name.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| filename | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only says 'delete,' which implies destructiveness. No details on error handling, reversibility, or side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Very concise single sentence, no fluff. However, brevity sacrifices essential parameter context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and two parameters, the description should at minimum explain what filename and name represent. It fails to do so, leaving the tool's usage unclear.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description does not explain the two parameters (filename and name). With 0% schema description coverage, the agent lacks context to understand what values to provide.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action (delete) and resource (slice), clearly distinguishing it from siblings like remove_tag or remove_frame. However, it could be more explicit about the filename parameter's role.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives, such as add_slice or set_slice. No prerequisites or conditions mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/MalloyTheDev/aseprite-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server