Skip to main content
Glama
Sign In
Chorono

Chorono

by codie1982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

control_playback

Control editor animation playback by playing, pausing, stopping, seeking, setting speed, and isolating timelines in the viewport; pass [] to restore all animations.

Instructions

Play, pause, stop or seek the editor; select a timeline and set speed. timelineIds isolates animations in the live viewport; [] restores all animations.

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": {
      "action": "<action>"
    },
    "name": "control_playback"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedNo
actionYes
timeMsNo
requestIdNo
sessionIdNo
timelineIdNo
timelineIdsNo
expectedRevisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already flag this as non-read-only and closed-world, so the mutation nature is covered structurally. The description adds real behavioral context beyond that by explaining that timelineIds isolates animations in the live viewport and that an empty array restores all animations. It omits what happens on seek without timeMs, whether speed persists across actions, and any concurrency behavior.

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?

Two compact sentences with the core actions front-loaded and the timelineIds caveat appended. No filler, though the semicolon structure slightly blurs the two distinct ideas.

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 an 8-parameter mutation tool with no output schema and no parameter descriptions, the definition is too thin. The missing semantics for timeMs and expectedRevision in particular leave an agent unable to invoke seek or optimistic-concurrency cases correctly.

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?

Schema coverage is 0% across 8 parameters, so the description must carry the burden and only partly does. It explains action, speed, and timelineIds, but leaves timeMs (essential for seek), timelineId vs timelineIds, expectedRevision, requestId, and sessionId entirely undefined.

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?

Names a specific verb set (play, pause, stop, seek) against a clear resource (the editor/timeline playback), so an agent can distinguish it from editing siblings like update_timeline or control_runtime. It does not explicitly contrast with those siblings, but the purpose itself is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent can infer this is the tool for transport control, and the timelineIds note hints at live-viewport isolation. There is no explicit guidance on when to use this versus control_runtime or evaluate_at_time, nor any stated preconditions.

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