Chorono

by codie1982

Overview Schema Source Related Servers Discussions Admin

add_layer

Add a new shape, text, media, repeater, or group layer to the Chorono scene; assign a unique id so you can target it with keyframes.

Instructions

Add a new layer to the scene. Set a meaningful id (e.g. "bg_rect", "title_text") — you will use this id in add_keyframes track targets.

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>",
      "name": "<name>",
      "type": "<type>"
    },
    "name": "add_layer"
  }
}

Input Schema

Name	Required	Description
`x`	No	X position in px (left edge of bounding box)
`y`	No	Y position in px (top edge of bounding box)
`id`	Yes	Unique layer id used to reference in keyframes
`loop`	No	Video/audio loop
`name`	Yes	Display name shown in the layer panel
`seed`	No	Blob deterministic seed integer
`text`	No	Text content (required when type=text)
`type`	Yes	Layer type
`count`	No	Repeater: number of copies
`endMs`	No	Time (ms) when layer disappears
`muted`	No	Video/audio muted
`phase`	No	Wave phase offset in radians
`sides`	No	Edge count for polygon/star (3-12) or blob (5-64)
`stepX`	No	Repeater linear: x offset per copy (px)
`stepY`	No	Repeater linear: y offset per copy (px)
`turns`	No	Spiral turn count (0.5–20)
`width`	No	Width in px
`height`	No	Height in px
`scaleX`	No	Horizontal scale (1 = 100%)
`scaleY`	No	Vertical scale (1 = 100%)
`volume`	No	Video/audio volume 0–1
`assetId`	No	Media: id of an existing scene asset (see list_assets)
`opacity`	No	Opacity 0-1
`startMs`	No	Time (ms) when layer becomes visible
`endAngle`	No	End angle for arc/ring in degrees
`fontSize`	No
`parentId`	No	Parent group layer id
`amplitude`	No	Wave peak height in px
`endRadius`	No	Spiral outer ending radius in px
`fillColor`	No	Fill hex color e.g. "#3B82F6"
`frequency`	No	Wave full-cycle count across width (0.1–50)
`objectFit`	No	Image fit mode (default contain)
`requestId`	No
`sessionId`	No
`shapeKind`	No	Shape geometry kind
`textAlign`	No
`textColor`	No
`tightness`	No	Spiral radius interpolation exponent (1=linear)
`fontFamily`	No
`fontWeight`	No
`startAngle`	No	Start angle for arc/ring in degrees
`stepScaleX`	No	Repeater: scaleX step per copy
`stepScaleY`	No	Repeater: scaleY step per copy
`fillOpacity`	No
`innerRadius`	No	Inner radius for star/ring
`polarRadius`	No	Repeater polar: ring radius (px)
`rotationDeg`	No	Rotation in degrees
`startRadius`	No	Spiral inner starting radius in px
`stepOpacity`	No	Repeater: opacity step per copy
`strokeColor`	No
`strokeWidth`	No
`cornerRadius`	No
`irregularity`	No	Blob noise ratio 0–1
`repeaterMode`	No	Repeater layout
`stepRotation`	No	Repeater: rotation step per copy (deg)
`letterSpacing`	No
`polarEndAngle`	No	Repeater polar: end angle (deg)
`sourceLayerId`	No	Repeater: id of the layer to repeat
`polarStartAngle`	No	Repeater polar: start angle (deg)
`expectedRevision`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, closed-world mutation, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the id becomes the reference handle for add_keyframes track targets — but says nothing about the expectedRevision concurrency parameter, what happens on duplicate id collisions, or that required fields vary by type.

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?

Two short sentences, both load-bearing: the first states the action, the second gives the id convention and its downstream consequence. Nothing redundant and no filler.

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 60-parameter creation tool with conditional required fields (text when type=text, assetId for media, sourceLayerId for repeaters) and an optimistic-concurrency parameter, the description covers only the id. The rich schema mitigates this, but key cross-parameter rules and mutation semantics are not addressed anywhere the agent will readily see them.

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 78%, so the schema carries most parameter meaning and the baseline is 3. The description adds a naming-convention example for id but is silent on the other 59 parameters, including expectedRevision and assetId (a required prerequisite for media types), which are the highest-risk inputs.

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?

States a specific verb and resource ("Add a new layer to the scene") and hints at its position in the workflow by naming add_keyframes as the downstream consumer. It does not explicitly separate itself from sibling creators like clone_layer, array_layer, or group_layers, so it stops short of a 5.

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 only implied: create a layer, then keyframe it by id. There is no explicit guidance on when to use add_layer versus clone_layer, array_layer, group_layers, or update_layer, and no prerequisites (e.g. assets must exist first for image/video/audio, groups must exist before parentId).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server