Skip to main content
Glama
Cavi Character Animator MCP

Cavi Character Animator MCP

Official
by cavi-ai

export_ingest

Creates a pinned media receipt and measured PCM audio descriptor for Unity cutscene delivery, writing outputs to a new directory while preserving editable project, performance, and XML provenance.

Instructions

Create a pinned media receipt and measured PCM audio descriptor for Unity cutscene delivery.

Outputs go into a new directory. Preserves editable project/performance/XML provenance; does not establish native rigging, lip-sync correctness, playback or visual acceptance.

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": {
      "recipe": "<recipe>",
      "directory": "<directory>"
    },
    "name": "export_ingest"
  }
}

Input Schema

NameRequiredDescriptionDefault
recipeYes
directoryYes

Output Schema

NameRequiredDescriptionDefault
nameYes
schemaYes
statusYes
handoffYes
versionYes
media_receiptYes
native_exportYes
cutscene_audioYes
launches_applicationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already declare a non-read-only, non-destructive, closed-world operation. The description adds useful behavioral context: outputs go into a new directory, editable provenance is preserved, and the tool explicitly does not establish rigging, lip-sync correctness, playback, or visual acceptance.

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 compact and front-loads the purpose in the first sentence. It avoids repetition and unnecessary detail, though the heavy jargon reduces immediate clarity.

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?

An output schema exists, so return values need not be described. However, with zero schema coverage for both required parameters and no real usage guidance, the description leaves important invocation details unspecified.

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 should compensate for the two required parameters. It only indirectly hints that "directory" is the output location and says nothing about what "recipe" means, its format, or valid values.

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 ("Create") and two deliverables ("pinned media receipt" and "measured PCM audio descriptor") scoped to "Unity cutscene delivery". It is clear enough to distinguish this from generic export or capture siblings, though it does not name alternatives 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?

Usage is only implied by the phrase "for Unity cutscene delivery." The description does not state when to use this instead of sibling tools such as export_inspect, scene_export, or capture, nor does it provide explicit exclusions.

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