Skip to main content
Glama
Sign In
Chorono

Chorono

by codie1982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_timeline

Create an animation timeline with a unique ID and duration before adding keyframes, and configure loop, autoplay, or ping-pong playback behavior.

Instructions

Create an animation timeline. You MUST create a timeline before calling add_keyframes. Set a meaningful id (e.g. "intro", "loop_anim") — you will reference it in add_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": {
      "id": "<id>",
      "durationMs": "<durationMs>"
    },
    "name": "create_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique timeline id e.g. "intro_anim"
loopNoLoop the timeline indefinitely
autoplayNoStart playing automatically on load
pingPongNoPlay forward then backward
loopCountNoNumber of loops (0 = infinite). Only when loop=true
requestIdNo
sessionIdNo
durationMsYesTotal timeline duration in milliseconds
expectedRevisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=false, so the agent already knows this is a closed-world mutation; the description adds useful lifecycle context (the created id becomes a reference key for later calls). However, it says nothing about collision behavior when the id already exists, what requestId/expectedRevision do for idempotency and optimistic concurrency, or whether creation is reversible.

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?

Three short sentences, zero filler, with the action and the hard prerequisite front-loaded before the naming advice. Nothing here could be removed without losing information.

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 9-parameter mutation tool with no output schema, the description covers purpose, ordering, and id semantics well but omits concurrency/idempotency semantics and failure modes. An agent could call it correctly in the happy path but would guess at what happens when the id collides or when expectedRevision is stale.

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 67%, and the description adds genuine meaning for `id` — that the value will be referenced later in add_keyframes — which goes beyond the schema's "Unique timeline id e.g. intro_anim". It leaves the three undocumented parameters (requestId, sessionId, expectedRevision) entirely unexplained, so it only partially compensates for the coverage gap.

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 leads with a specific verb+resource ("Create an animation timeline") that clearly separates it from update_timeline, clone_timeline, delete_timeline, and list_timelines. It stops just short of naming a sibling alternative outright, but the prerequisite statement makes the create-vs-modify distinction obvious.

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?

Strong sequencing guidance: it states the hard prerequisite ("You MUST create a timeline before calling add_keyframes") and gives concrete id conventions with examples. What's missing is guidance on when to use this versus clone_timeline for duplicating an existing timeline, or what to do if the id already exists.

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