Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

list_slices

Read-only

Lists every slice with its bounds, pivot, and 9-patch center; read-only and supports headless use by passing a file.

Instructions

List every slice with its bounds, pivot, and 9-patch center. Read-only. Headless: pass file.

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

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, so "Read-only" adds nothing. The headless note is genuinely new behavioral context, but the description never explains what moderation the `file` argument unlocks or whether the tool behaves differently with versus without 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?

Two short sentences, front-loaded with the return contents and followed by the operational caveat. Tight and waste-free, though the telegraphic "Headless:" fragment is slightly cryptic without prior context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter read tool with no output schema, stating read-only status, the returned fields, and the headless file requirement covers most of what an agent needs. The remaining gap is the undefined meaning of `file`.

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 coverage is 0%, so the description must compensate for the single `file` parameter, and it partially does by tying it to headless mode. However it never says what the file is (project, sprite sheet, config) or what happens when it is omitted in a headless run, leaving the key ambiguity unresolved.

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?

Specific verb and resource ("List every slice") plus the exact fields returned (bounds, pivot, 9-patch center), which tells an agent what it gets. It does not explicitly contrast with sibling export_unity_slices, so differentiation relies on the verb alone.

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?

The "Headless: pass ``file``" line gives a conditional usage instruction, implying the parameter is only needed in headless contexts. There is no statement of when to prefer this over export_unity_slices or other inspection tools, so guidance is implied rather than explicit.

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