Retrieve sprite size, color mode, layers, frame durations, tags, and optional palette colors from an Aseprite file to inspect animation and structure.
Size, mode, layers, frame durations, tags. palette=true adds palette colors.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| palette | No |
Changes observed during successful MCP inspections.
v2.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the returned fields and the effect of palette=true, but omits whether the tool is read-only, requires an existing file, or can fail.
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?
The description is compact and front-loads the returned fields. It is terse but not padded, though the fragmentary structure leaves it slightly under-specified.
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?
For a simple two-parameter info tool with no output schema, it lists the main return fields and explains the palette flag. However, it leaves the required path parameter and usage context unaddressed.
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?
Schema coverage is 0%, so the description must compensate. It explains palette=true adds palette colors, but does not describe the required path parameter or what path refers to.
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 specifies the sprite metadata returned: size, mode, layers, frame durations, and tags, with an optional palette addition. This makes the tool’s purpose clear, though it does not explicitly differentiate it from siblings like palette or read_pixels.
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?
There is no guidance on when to use this tool versus alternatives such as palette or read_pixels. The only usage-like detail is the local effect of palette=true, not tool selection guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.