Skip to main content
Glama

gait

Generate walking, trotting, or galloping cycles on rigs with foot IK targets and a body bone. Key planted stance, swing arc, toe roll, body bob, and sfx_step events.

Instructions

Key a gait on ANY rig that has foot IK targets and a body bone: planted stance, swing arc, toe roll, body bob and pitch coupled to the footfalls, and an sfx_step event (string = leg name) at every touch-down. Call with no project to list the gaits.

gait: walk (4-beat LH LF RH RF), trot (diagonals), pace (laterals), canter (3-beat), gallop (rotary, two flights), bound (hind pair / fore pair) for 4 legs; tripod (L1 R2 L3 / R1 L2 R3) and wave for 6; biped_walk / biped_run for 2 ("walk"/"run" resolve by leg count). legs: the foot IK target bones, e.g. ["ik_front_L", "ik_front_R", "ik_hind_L", "ik_hind_R"]; side and end are read from the name (_L/_R, front/hind/middle, LF, RH, L1..R3) or given as dicts {"target", "side": "L|R", "end": "front|middle|hind", "name", "roll", "hip", "reach", "offset", "bias"}. Hip, reach and the hock offset are found from the IK constraint that serves each target. body: the bone that bobs and pitches (its children carry the hips/shoulders; the targets must NOT be under it). speed: units/s (default: the gait's typical speed in leg lengths/s x the hip height). The cycle is in place; the game scrolls the world at this speed. Frequency f = c sqrt(speed / leg_length), stride = speed / f, so speed scales both by sqrt; if a stride would over-stretch a leg the frequency is raised (reported). frequency / duty / clearance / bob / pitch / roll: overrides (0 or -1 = gait default; clearance and bob in units, pitch and roll in degrees). exaggerate scales clearance, bob, pitch and roll. facing: 1 right, -1 left, 0 auto (front feet ahead of hind feet). Loops close exactly; keys go into animation name (default the gait's name), at start, cycles strides long.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bobNo
bodyNo
dutyNo
gaitNowalk
legsNo
nameNo
rollNo
pitchNo
speedNo
startNo
cyclesNo
eventsNo
facingNo
projectNo
clearanceNo
frequencyNo
exaggerateNo
leg_lengthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the key mutation effect, sfx_step events at touch-down, exact loop closure, speed/frequency/stride coupling, override behavior, and reporting of over-stretched legs. This is richly transparent for a complex rigging tool.

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?

Long but dense and front-loaded: it begins with the core action, then labels parameter groups. For an 18-parameter rigging tool, each sentence contributes eligibility rules, parameter meaning, or behavioral detail without padding.

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?

Given high complexity, no annotations, and no output schema, the description is largely complete. It lacks explicit return or error behavior for the keying mode, only implying the listing behavior when no project is supplied, which is a minor gap for a mutation tool without an output schema.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 18 parameters, so the description must compensate. It explains gait values by leg count, leg target structure and name parsing, body role, speed defaults and formulas, override semantics for frequency/duty/clearance/bob/pitch/roll, exaggerate, facing, name, start, and cycles. It meaningfully covers nearly all parameters.

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?

States a specific verb and resource: 'Key a gait' on any rig with foot IK targets and a body bone. It also explains the no-project listing mode. It does not explicitly differentiate from siblings such as add_keys or rig_quadruped, so sibling differentiation is absent.

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?

Gives clear prerequisites ('ANY rig that has foot IK targets and a body bone') and a special usage mode: 'Call with no project to list the gaits.' However, it does not say when not to use it or name alternative tools, so exclusions are missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.