Skip to main content
Glama
Cavi Character Animator MCP

Cavi Character Animator MCP

Official
by cavi-ai

export_inspect

Read-onlyIdempotent

Validates ordered native-export PNG, WAV, and source hashes plus exact dialogue sample timing in existing files, confirming export integrity without running a new Character Animator export.

Instructions

Validate explicitly ordered native-export PNG/WAV/source hashes and exact dialogue sample timing.

Frame rate/order are caller declarations; proprietary project/puppet files are opaque provenance. This inspects existing files and does not perform a native Character Animator 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": {
      "recipe": "<recipe>"
    },
    "name": "export_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
recipeYes

Output Schema

NameRequiredDescriptionDefault
fpsYes
nameYes
schemaYes
statusYes
versionYes
durationYes
frame_countYes
native_exportYes
frame_rate_sourceYes
frame_order_sourceYes
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?

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: frame rate and ordering are caller declarations rather than verified facts, and proprietary project/puppet files are treated as opaque provenance — telling the agent exactly what the validation does and does not certify.

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?

Three short sentences with a clean progression: what it validates, what it treats as untrusted, and what it explicitly does not do. No filler, and the core purpose is front-loaded; density of specialized vocabulary ('caller declarations', 'opaque provenance') costs some immediate readability.

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?

Annotations and the existing output schema relieve the description of safety and return-value duties, but the sole input 'recipe' receives no coverage anywhere in the definition. For a validation tool whose entire contract depends on how the recipe is structured, that is a substantive hole an agent cannot fill from structured fields.

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?

There is a single required parameter, 'recipe', with 0% schema description coverage, and the description never explains what a recipe is, its format, or how its ordering semantics work. The phrase 'explicitly ordered' gestures at ordering being encoded in the recipe, but that is inference rather than definition, leaving the only input effectively undocumented.

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?

A specific verb ('Validate') applied to concrete resources (PNG/WAV/source hashes, dialogue sample timing), which is far more than a restatement of 'export_inspect'. The final sentence carves out its scope ('inspects existing files and does not perform a native ... export'), which separates it from export-producing siblings, though the jargon-heavy phrasing makes the purpose slower to grasp than it needs to be.

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?

The closing line implies when NOT to use it (no export is performed), which is a useful negative signal, and 'Validate explicitly ordered ... hashes' implies the pre-condition that an export already exists. However, there is no positive trigger telling the agent when to reach for this versus export_ingest or inspect, and no prerequisites are stated.

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