Skip to main content
Glama
Sign In
Chorono

Chorono

by codie1982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remove_track

Remove an animation track from a specified timeline to clean up or simplify a Chorono project.

Instructions

Remove an animation track from an explicit timeline.

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": "remove_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
requestIdNo
sessionIdNo
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?

The annotations establish that this is a non-read-only, non-open-world operation, and the description adds that it removes a track. However, it does not disclose whether removal is destructive or reversible, what happens to keyframes or modifiers on the track, or how expectedRevision affects 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?

The description is a single front-loaded sentence with no wasted wording. Its concision is appropriate, though the sentence is too sparse to carry much operational meaning.

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 mutation tool with five parameters, no output schema, and zero schema description coverage. A one-sentence description does not provide enough context to safely invoke it, especially around target semantics, concurrency, and side effects.

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 description coverage is 0%, so the description must compensate for five undocumented parameters. It only loosely implies that target is the track and timelineId identifies the timeline, and says nothing about requestId, sessionId, or expectedRevision.

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 and resource: remove an animation track. It also scopes the operation to an explicit timeline, which distinguishes it from timeline-level deletion tools such as delete_timeline. However, it does not explicitly differentiate from closely related siblings like update_track or bake_track.

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?

The description gives no guidance on when to use this tool versus alternatives such as update_track, bake_track, or delete_timeline. It also omits prerequisites, such as whether the track must already exist or whether removal affects associated keyframes.

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