Skip to main content
Glama
Sign In
Chorono

Chorono

by codie1982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_keyframes

Add or replace keyframes on a timeline layer property to control animation timing and values, including custom Bezier easing for precise motion.

Instructions

Add or replace keyframes on an explicit timeline and layer property. Supports customBezier with {type:"customBezier",bezier:{cx1,cy1,cx2,cy2}}. Easing belongs to the starting keyframe.

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>",
      "layerId": "<layerId>",
      "property": "<property>",
      "keyframes": "<keyframes>"
    },
    "name": "set_keyframes"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerIdYes
propertyYes
keyframesYes
requestIdNo
sessionIdNo
timelineIdYes
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 declare readOnlyHint=false and openWorldHint=false, so the write nature is already known. The description adds genuinely new behavioral detail beyond the annotations: the operation replaces existing keyframes, easing is attributed to the starting keyframe, and customBezier accepts a specific bezier object shape. It omits conflict handling (`expectedRevision`), idempotency (`requestId`), and what happens to keyframes not passed in.

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 sentences, front-loaded with the primary action and its scope, then the format detail. The inline JSON snippet is dense but earns its place because the schema types `easing` as an empty object. Only minor tightening is possible.

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?

This is a mutating tool with no output schema, no annotation detail beyond read/write, and zero schema description coverage. The description should have covered revision semantics, the required parameter roles, and any error/conflict behavior; it addresses only the easing format, so an agent is left guessing on most of the call surface.

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 description coverage is 0%, so the description must compensate and it does so only partially: the schema leaves `easing` and `value` as untyped `{}`, and the description fills that gap with the customBezier structure and the starting-keyframe rule. Six of seven parameters, notably `expectedRevision` (a concurrency token) and `requestId`, receive no explanation at all.

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 states a specific verb pair ("Add or replace") and resource ("keyframes") scoped to an explicit timeline and layer property, which is concrete. It does not, however, distinguish itself from the sibling tool `add_keyframes`, leaving the agent to guess which of the two to call.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the obvious alternative (`add_keyframes`) or prerequisites such as a valid timeline/layer. The only usage-adjacent information is the implicit requirement that the timeline and property be explicitly identified.

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