Skip to main content
Glama
Cavi Character Animator MCP

Cavi Character Animator MCP

Official
by cavi-ai

project_prepare_copy

Copies a closed saved .chproj workspace to a new location and verifies its file hashes before native opening, producing a prepared copy for inspection and session claiming.

Instructions

Copy a closed saved workspace .chproj tree and verify its file hashes before native opening.

The source must not be open in Character Animator. This creates only a new workspace copy; pass its prepared_copy_id to project_open_prepared_copy, inspect the opened root, then claim it with session_control and the same prepared_copy_id.

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": {
      "source": "<source>",
      "destination": "<destination>"
    },
    "name": "project_prepare_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
destinationYes

Output Schema

NameRequiredDescriptionDefault
filesYes
sourceYes
statusYes
destinationYes
source_identityYes
prepared_copy_idYes
destination_identityYes
launches_applicationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish that this is not read-only, not destructive, and closed-world. The description adds useful behavioral context beyond them: the source must be closed, the copy is only a new workspace copy, file hashes are verified, and the resulting prepared_copy_id drives the follow-on inspection and claim workflow. It does not describe destination overwrite or error behavior.

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?

The description is three sentences, front-loaded with the core action and followed by the prerequisite and exact handoff workflow. Every sentence contributes operational information, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It covers the critical workflow and prerequisite for a copy-preparation tool, and the output schema reduces the need to explain return values. However, both required parameters have zero schema descriptions and the destination semantics are not explained, leaving an invocation-level gap despite the useful annotations and follow-on guidance.

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 the undocumented source and destination parameters. It partially clarifies source by requiring a closed saved workspace .chproj tree that is not open, but it says nothing about what destination represents, whether it is a directory or file target, or how existing content there is handled.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: copying a closed saved workspace .chproj tree and verifying its file hashes. It also clarifies that this creates only a new workspace copy and hands off to project_open_prepared_copy, which distinguishes the operation from simply opening or saving a project.

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?

It gives clear usage context and prerequisites: the source must not be open in Character Animator, and the prepared_copy_id must be passed to project_open_prepared_copy, inspected, and then claimed via session_control. It does not explicitly state when to choose project_save_copy or other alternatives, so it is not fully exhaustive.

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