Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

swing_part

Animate a pixel-art wing, arm, tail, or ear swinging around its joint across frames. Define the part's outline and pivot, then set per-frame angles to rotate it without opening gaps at the body.

Instructions

Swing a wing, arm, tail or ear about its joint across frames. outline is a polygon round the part, in canvas pixels [[x, y], ...]; keep it to the part itself (not the face or chest beside it). pivot is the joint. keys, one per frame (frames are made as needed): {"frame": 2, "angle": 10, "dx": 0, "dy": -1, "ms": 90}, angle in degrees clockwise. Where the part met the body, a band of shadow (the part's darkest colour by default) stays underneath, so turning never opens a gap, and the part's light outer halo is dropped so it doesn't streak. Small angles (up to about 15) look best. 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": {
      "outline": "<outline>",
      "pivot": "<pivot>",
      "keys": "<keys>"
    },
    "name": "swing_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandNo
fileNo
keysYes
layerNo
pivotYes
shadowNo
outlineYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

The only annotation is a title, so the description carries the full burden and does a good job: it discloses that frames are created as needed, that one undo step is recorded, that a shadow 'band' is retained and the outer halo dropped, and that headless use requires `file`. Permission/auth requirements and error behavior are not covered, which prevents a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, then parameter semantics, then the non-obvious rendering side effects (shadow band, dropped halo) and the headless note. Every sentence carries information an agent could not get from the schema; nothing is padded.

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 seven-parameter mutation with no output schema and no behavioral annotations, the description covers the workflow, key data shape, visual side effects, and headless mode. The unexplained `layer` parameter is the one real hole.

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

Parameters4/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 compensate, and it does for six of seven parameters: outline format and its exclusion of face/chest, pivot as the joint, the keys object shape with a concrete example and clockwise degrees, shadow defaulting to the part's darkest colour, and the band. `layer` is never mentioned, leaving one parameter unexplained in both schema and description.

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 opening sentence gives a concrete verb and resource ('Swing a wing, arm, tail or ear about its joint across frames'), so the agent knows the operation and the kinds of parts involved. It does not name or distinguish itself from plausible siblings such as animate_parts or bob_body, which keeps it short of a 5.

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?

Usage context is implied rather than stated: 'Small angles (up to about 15) look best' and 'Headless: pass file' tell the agent how to call it well, but there is no explicit when-to-use/when-not or comparison against the other animation tools in the catalog.

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