Skip to main content
Glama
Sign In
Chorono

Chorono

by codie1982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

clear_scene

Remove all layers and timelines to reset the scene. Use it before generating a complete new animation from scratch.

Instructions

Remove all layers and timelines from the scene (fresh start). Use before generating a complete new animation from scratch.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clear_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdNo
sessionIdNo
expectedRevisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 mutating, local nature of the call is already structured data. The description adds real value by disclosing the destructive scope ('all layers and timelines'), but omits whether the wipe is reversible, whether it can be undone, and what happens to assets or sessions.

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, the destructive scope front-loaded ahead of the usage note. Nothing is padded and nothing needs reordering.

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 destructive, scene-wide operation with three undocumented parameters and no output schema. For that risk profile, the definition should at minimum address reversibility/undo and the meaning of expectedRevision, neither of which appears.

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% and the description explains none of the three parameters. The presence of `expectedRevision` strongly implies optimistic concurrency and `requestId` implies idempotency, but the agent gets no hint of either, nor of how `sessionId` scopes the operation.

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 all layers and timelines from the scene' — with the clarifying parenthetical '(fresh start)'. It is distinguishable from single-target siblings like delete_layer and delete_timeline by the word 'all', though it never names those siblings explicitly.

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?

It gives one clear when-to-use: 'Use before generating a complete new animation from scratch.' There is no when-not guidance, no mention of when to prefer delete_layer/delete_timeline for partial cleanup, and no note that an `undo` sibling exists as a recovery path.

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