Skip to main content
Glama

apply_timing_curve

Adjust animation timing with curves that set frame durations for holds, snaps, and easing without duplicating frames.

Instructions

Give an animation a shape in time, by setting durations and never duplicating frames.

Uniform timing is the placeholder every animation starts with and almost none should
keep. A cycle holds its extremes two to four times as long as the poses it passes
through; an attack holds the anticipation, snaps through the strike in 20 to 40ms, and
holds the impact.

Args:
    curve: `hold_extremes` (the ends of a cycle are held, the passing frames are not),
        `attack` (anticipation, snap, impact, recovery), `ease_in` (starts slow),
        `ease_out` (ends slow), or `flat` (every frame the same, to start over).
    frames: The frames to time, in order. Defaults to a tag's frames, or all of them.
    tag: Time one tag's frames instead of naming them.
    base_ms: The duration of a passing frame. Everything else is a multiple of it.
    hold_frames: Frames to hold whatever the curve says, at three times `base_ms`.
    snap_frames: Frames to snap through, at the shortest duration that still registers.

A hold is a longer duration on one frame, never a repeated frame: duplicating costs a
frame, shifts every tag index, and hides the repeat from `validate_loop`. The returned
`frames_added` is always 0, and it is returned so that claim can be checked.

Easing here and easing the spacing elsewhere are the same curve applied twice, which
reads as slow motion rather than as weight. The cels are measured on the way through,
so asking for an eased curve over spacing that is already eased comes back with a
warning rather than quietly doing it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNo
curveNoDefault: "hold_extremes".hold_extremes
framesNo
base_msNoDefault: 100.
filenameYes
hold_framesNo
snap_framesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false; the description carries the rest and does so richly: holds are durations not duplicated frames, duplicating shifts every tag index and hides the repeat from validate_loop, frames_added is always 0 and returned so the claim is checkable, and a double-ease request returns a warning rather than silently proceeding.

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?

Front-loaded with the purpose sentence and structured into prose rationale followed by an Args list. The aphorism about uniform timing being a placeholder is mildly expendable, but the rest earns its place.

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?

No output schema, yet the description explains the meaningful return value (frames_added always 0) and the warning path, which is more than required. The main omission is the required `filename` parameter, and the warning's exact shape is not spelled out.

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 coverage is only 29% and there are no enums, so the description does the heavy lifting: it enumerates and explains all five `curve` values, defines base_ms as the passing-frame duration with everything else a multiple of it, and clarifies hold_frames (3x base_ms) and snap_frames (shortest registrable duration). Only the required `filename` is left undocumented.

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 opening states a specific verb+resource: 'Give an animation a shape in time, by setting durations.' The 'never duplicating frames' clause and the curve taxonomy distinguish it from generic siblings like set_frame_duration and set_all_frame_durations.

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 concrete when-to-use guidance per curve ('a cycle holds its extremes two to four times as long as the poses it passes through', attack = anticipation/snap/impact), plus an explicit when-not-to-do-something warning about combining easing here with eased spacing. It stops short of naming sibling alternatives like set_frame_duration.

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