Skip to main content
Glama
Cavi Character Animator MCP

Cavi Character Animator MCP

Official
by cavi-ai

project_select

Destructive

Selects one uniquely OCR-matched Project-panel row by name and item type, using a fingerprint check and optional extend for additive selection.

Instructions

Select one uniquely OCR-matched Project-panel row by name and type.

extend controls additive selection; use the latest inspect fingerprint. OCR evidence is not a scene 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": {
      "name": "<name>",
      "item_type": "<item_type>",
      "extend": "<extend>",
      "expected_fingerprint": "<expected_fingerprint>",
      "lease_id": "<lease_id>"
    },
    "name": "project_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
extendYes
lease_idYes
item_typeYes
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault
nameYes
extendYes
nativeYes
statusYes
item_typeYes
completionYes
retry_safeYes
operation_idYes
selection_evidenceYes
expected_state_fingerprintYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds one real behavioral fact: extend makes selection additive rather than replacing. However, it never says what the destructive side effect actually is (discarding an existing selection? mutating session state?), nor what the lease/fingerprint preconditions do on mismatch. That gap matters for a destructive tool.

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, front-loaded with the action and its constraint; each sentence carries distinct information, including the 'OCR evidence is not a scene ID' caveat. The phrasing is dense and jargon-heavy but not padded.

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 described. Still, with five required parameters at 0% schema coverage and a destructive annotation, the definition leaves lease_id undefined and gives no precondition or failure behavior, which is thin for a state-mutating tool.

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%, so the description must carry all five required parameters. It does explain extend (additive), name/item_type (uniqueness matching), and expected_fingerprint (latest inspect fingerprint), but lease_id is never mentioned and no formats or matching rules are given, so compensation is only partial.

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?

States a specific verb and resource ('Select one uniquely OCR-matched Project-panel row by name and type'), which is far more precise than a generic 'select row'. It does not name or contrast any sibling, so an agent must infer how this differs from inspect or scene_action.

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?

Gives two usable operating conditions: 'extend controls additive selection' and 'use the latest inspect fingerprint', which implicitly routes the agent to inspect first. It never states when not to use it, what happens on ambiguous matches, or whether a non-extend call replaces the current selection.

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