Skip to main content
Glama
Cavi Character Animator MCP

Cavi Character Animator MCP

Official
by cavi-ai

project_open_prepared_copy

Opens the exact closed-project copy created by project_prepare_copy so you can inspect its native root and claim it using the matching prepared_copy_id.

Instructions

Open only the exact closed-project copy previously prepared by project_prepare_copy.

Inspect the opened native 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": {
      "prepared_copy_id": "<prepared_copy_id>"
    },
    "name": "project_open_prepared_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
prepared_copy_idYes

Output Schema

NameRequiredDescriptionDefault
nativeYes
statusYes
completionYes
project_idYes
retry_safeYes
operation_idYes
prepared_copy_idYes
launches_applicationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description is consistent with a non-destructive state-changing open. Beyond annotations it adds real behavioral context: opening alone does not establish a usable session — the caller must inspect the native root and claim it with session_control using the same id. It does not cover failure modes (invalid/expired id, already-open copy) or whether the prepared copy is consumed.

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 sentences, front-loaded with the core action and constraint, then the required follow-on. No restated name/title and nothing that could be cut without losing information.

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

Completeness4/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, and for a single-parameter tool the description covers the essential workflow (prepare → open → inspect → claim). The remaining gap is error/recovery behavior for an invalid or already-used prepared_copy_id.

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?

There is one parameter with 0% schema description coverage, so the schema alone says nothing. The description supplies provenance ('the same prepared_copy_id' produced by project_prepare_copy and reused for session_control), which adds meaning, but gives no format, validation, or reuse semantics, so it only partially compensates for the coverage gap.

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?

States a specific verb ('Open') scoped to an exact resource ('the exact closed-project copy previously prepared by project_prepare_copy'). It distinguishes itself from siblings by naming the producer tool (project_prepare_copy) and the follow-on tool (session_control), so an agent can route correctly without opening any schema.

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?

Gives a clear precondition (the copy must have been prepared by project_prepare_copy) and an explicit post-condition workflow ('Inspect the opened native root, then claim it with session_control'). It lacks an explicit exclusion, e.g. what to do if the project is already open or the id is stale, so it falls short of the 5 mark.

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