Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

bob_body

Animate breathing, hops, and sways by moving only the pixels above feet_y, keeping feet planted. Keys set per-frame dx/dy offsets in a single undo step.

Instructions

Breathing, hops and sways: everything above the row feet_y moves while the feet below it stay planted. Put feet_y at the top of the feet. keys, one per frame (frames are made as needed): {"frame": 1, "dy": -1, "dx": 0, "ms": 160}; -1 rises a pixel (the legs stretch), +1 sinks. Breathing is 0/-1; a hop -2..-4; a sway dx -1/+1. 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": {
      "feet_y": "<feet_y>",
      "keys": "<keys>"
    },
    "name": "bob_body"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
keysYes
layerNo
feet_yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

The description adds useful behavioral details beyond the sparse annotations: 'One undo step' and 'frames are made as needed', plus headless mode requiring file. It does not state broader side effects, whether existing frames are modified, or permission requirements for a mutation tool.

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?

The description is dense but front-loaded: it states the core effect first, then technical details. Every sentence carries actionable information, though the code-like phrasing and inline JSON make it less scannable than it could be.

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 mutation tool with four parameters, no output schema, and only minimal annotations, the description covers the essential animation mechanics and key parameter semantics. It is incomplete about the optional layer parameter and does not clarify return behavior or failure modes.

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 carry parameter meaning. It explains feet_y, the keys object format, dy/dx value semantics, and the file parameter for headless use. It leaves the 'layer' parameter completely undocumented and only partially explains 'ms' and 'frame'.

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 animation action: body bobbing (breathing, hops, sways) while feet below feet_y stay planted. It distinguishes this from a generic motion tool by explaining the feet-planted constraint. However, it does not name or contrast with sibling tools like ambient_motion or animate_parts.

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?

It gives practical guidance for key values (breathing 0/-1, hop -2..-4, sway dx -1/+1) and where to place feet_y, which helps with invocation. But it offers no explicit when-to-use versus alternatives, nor any when-not-to-use conditions.

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