Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

walk_cycle_template

Lay down a timed, tagged walk or run cycle skeleton with a locked faded guide layer and empty art layer, so you can draw frames over it for in-place game animation.

Instructions

Lay down a timed, tagged walk or run skeleton to draw over. It adds frames frames (an even number, 4-16), or uses the sprite if it's a blank single frame, with a locked faded guide layer and an empty art layer above it, which it leaves active. The near limbs are light blue and the far limbs dark blue. Feet travel backward on the ground and swing forward through the air, so the cycle walks forward; the figure stays in place, ready for scrolling scenery or game movement. Check it with look_animation, then hide or delete the guide. 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": {
      "body_height": "<body_height>"
    },
    "name": "walk_cycle_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
fileNo
gaitNowalk
facingNoright
framesNo
body_heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior5/5

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

With only a title annotation, the description carries the full burden and does well: it discloses that the guide layer is locked and faded, that a new empty art layer is created and left active, limb coloring (near light blue, far dark blue), that the figure stays in place while feet travel backward, and that the whole operation is one undo step. It also flags the blank-single-frame fallback and headless file mode.

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?

It is front-loaded with the action and outcome, then follows with color, motion, verification, and headless notes in a logical order. The stray duplication of '``frames`` frames' is a minor artifact, and every other sentence carries distinct information.

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 six-parameter generator tool with no output schema and bare annotations, the description covers the essential behavior, side effects, and verification path. The main gap is the missing explanation of the required ``body_height`` and of ``tag``, which an agent cannot infer for context.

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 has to explain the parameters, and it only partly does: it explains ``frames`` (even, 4-16) and ``file`` (headless), and it implies ``gait`` via 'walk or run' and ``facing`` via 'the cycle walks forward.' The required ``body_height`` and the ``tag`` parameter are never explained, so three of six parameters remain opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Lay down a timed, tagged walk or run skeleton to draw over,' and then specifies exactly what is produced: a locked faded guide layer with an empty art layer above it. This makes the tool clearly distinct from the sibling tools that only verify or animate, such as look_animation and 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives real workflow guidance ('Check it with look_animation, then hide or delete the guide') and a headless-mode instruction ('pass ``file``'), plus the precondition that it uses the sprite if it is a blank single frame. It does not state when to choose a run vs walk gait or when not to use it, but the context it provides is clear.

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