Skip to main content
Glama
Sign In
Chorono

Chorono

by codie1982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bake_track

Convert procedural animation and modifiers into editable linear keyframes so you can manually adjust timing, refine motion, and ensure predictable playback.

Instructions

Bake procedural animation/modifiers into editable linear keyframes.

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": {
      "timelineId": "<timelineId>",
      "target": "<target>"
    },
    "name": "bake_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNo
targetYes
requestIdNo
sessionIdNo
toleranceNo
timelineIdYes
expectedRevisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description still owes the agent the important behavioral facts: whether baking removes or retains the source modifiers/emitter, whether it replaces existing keyframes on the target track, and how fps and tolerance affect sampling density. The phrase 'editable linear keyframes' does disclose the resulting interpolation type, which is a small genuine addition, but the destructive/replacement semantics are unstated.

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?

A single front-loaded sentence with no filler or redundant restatement of the tool name. It is efficient, but its brevity is under-specification rather than disciplined compression given the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with seven parameters, no output schema, no annotations beyond the safety flags, and no parameter documentation, the description leaves the agent unable to call it correctly without guessing. Nothing is said about what happens to the source procedural data or what revision/request identifiers do.

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

Parameters2/5

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

Seven parameters with 0% schema description coverage, and the description explains none of them. The meaning of 'tolerance' (sampling error threshold?), 'fps' (bake sample rate?), and 'expectedRevision' (concurrency guard?) is entirely undocumented, and 'target' could be a layer, track, or entity with no disambiguation from the text.

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 names a specific operation ('bake') plus resource ('procedural animation/modifiers') and states the output form ('editable linear keyframes'), which is more informative than a restated name. It does not, however, distinguish itself from nearby siblings such as add_modifier, add_keyframes, or set_keyframes, leaving the agent to infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternative is named despite the sibling list containing obvious candidates (add_modifier for staying procedural, add_keyframes/set_keyframes for authoring keys directly). The agent must guess the workflow position of baking from the word alone.

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