Skip to main content
Glama
Cavi Character Animator MCP

Cavi Character Animator MCP

Official
by cavi-ai

character_status

Read-onlyIdempotent

Verifies Adobe Character Animator app and control availability without launching it, recording, or triggering permission prompts, so you can confirm readiness before starting work.

Instructions

Inspect app/control availability without launch, recording or permission prompts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "character_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
nativeYes
reasonYes
availableYes
connectedYes
launches_applicationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavioral value by clarifying that the call does not launch anything, does not start a recording, and does not trigger permission prompts — side effects an agent would otherwise have to guess at.

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?

A single front-loaded sentence with no filler; the non-side-effect guarantees are stated compactly and immediately.

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 a zero-parameter read-only tool needs little more than the side-effect disclaimer provided. The only residual gap is that the description never clarifies what "character" state is actually being reported, which matters given the name.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description does not need to explain any inputs and introduces no misleading parameter expectations.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Inspect app/control availability" gives a verb and an object, but "availability" is abstract and the term does not map cleanly onto the tool name character_status, so an agent cannot confidently predict what state is being reported. It also offers no differentiation from siblings like inspect or session_control.

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 phrase "without launch, recording or permission prompts" implicitly frames this as a cheap pre-flight check to run before those heavier actions, which is useful implied guidance. However, no alternative tool is named and no explicit when-not-to-use condition is stated.

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