Skip to main content
Glama
Cavi Character Animator MCP

Cavi Character Animator MCP

Official
by cavi-ai

scene_export

Destructive

Submits the current owned scene's PNG sequence and WAV to a new workspace directory and confirms native chooser submission; use export_inspect to verify actual files afterward.

Instructions

Submit PNG Sequence and WAV for the current owned scene into a new workspace directory.

The result confirms native chooser submission only. Inspect actual files with export_inspect after export.

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": {
      "directory": "<directory>",
      "name": "<name>",
      "expected_fingerprint": "<expected_fingerprint>",
      "lease_id": "<lease_id>"
    },
    "name": "scene_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
lease_idYes
directoryYes
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault
nativeYes
statusYes
retry_safeYes
operation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the mutation profile is covered. Beyond that, the description adds genuinely new context: the return value only acknowledges native chooser submission and is not proof the files landed, which prevents premature success reporting. It still does not explain what is overwritten or what 'owned scene' means.

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 tight sentences: the operation and target come first, the result caveat and the follow-up tool second. No filler and nothing is buried.

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 four-parameter, all-required destructive operation, the definition leaves the caller guessing at lease_id and expected_fingerprint semantics, which are the parameters most likely to cause a failed or wrong submission. An output schema exists, so return shape need not be explained, but the behavioral and parameter gaps are still substantial.

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% across four required parameters, and the description never mentions 'name', 'lease_id', or 'expected_fingerprint'. It only indirectly gestures at 'directory' via 'new workspace directory'. Concurrency leases and fingerprint validation are safety-relevant for a destructive export and are entirely undocumented here.

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 names a specific action (submit/export) and specific artifacts (PNG Sequence and WAV) for the 'current owned scene' into a 'new workspace directory', which is far more concrete than a restated title. It does not explicitly contrast itself with export_ingest or capture, so the differentiation from siblings is only partial.

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

Usage Guidelines4/5

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

The description gives a clear follow-up rule: use export_inspect after export because the result only confirms chooser submission, not file contents. It does not state preconditions or when to prefer an alternative export path, but the post-export guidance is explicit and actionable.

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