Skip to main content
Glama
Cavi Character Animator MCP

Cavi Character Animator MCP

Official
by cavi-ai

project_save_copy

Destructive

Saves the current Character Animator project as a copy in a new workspace directory, then verifies the root and project files without editing the source scene or discarding unsaved state.

Instructions

Native Save Project As into a new workspace project, then verify actual root and project files.

directory is an existing parent; name is a safe ASCII project name. Does not edit the source scene or discard unsaved state. A missing original file hash remains explicitly unavailable.

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>",
      "lease_id": "<lease_id>"
    },
    "name": "project_save_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
lease_idYes
directoryYes

Output Schema

NameRequiredDescriptionDefault
filesYes
statusYes
project_idYes
retry_safeYes
operation_idYes
project_fileYes
project_rootYes
source_identityYes

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 destructiveHint=true, so the description's clarification that it does not edit the source scene or discard unsaved state meaningfully narrows what 'destructive' means here. It also discloses a verification step and an edge case about a missing original file hash, adding real behavior beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the text is short, but phrasing is dense and slightly opaque ('verify actual root and project files', 'a missing original file hash remains explicitly unavailable'), which reads as internal jargon rather than guidance.

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?

An output schema exists, so return values need not be explained, and the mutation's safety profile is partly covered. However, a required lease_id with no explanation and no routing relative to the prepare/open copy siblings leaves an agent with gaps before it can invoke this confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description rescues two of three parameters by explaining that directory is an existing parent and name is a safe ASCII project name. The required lease_id is never mentioned in either the schema or the description, leaving a genuine gap.

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 outcome: perform a native 'Save Project As' into a new workspace project, then verify the resulting root and project files. That is concrete enough to distinguish it from project_prepare_copy/project_open_prepared_copy, 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 Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and no alternative is named despite several copy/prepare siblings. The only usable context is a precondition (directory must be an existing parent, name must be safe ASCII), which is prerequisite info rather than selection guidance.

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