Skip to main content
Glama
Sign In
mcp-for-cascadeur

mcp-for-cascadeur

by Rickcy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

character_retime

Destructive

Retimes 2-8 synchronized character keys to authored Point targets, preserving metadata and validating poses, protected channels, and body connections; optional stationary-foot stabilization.

Instructions

Retime 2-8 synchronized character keys using authored Point targets, validated finger-local rotations and settings. Preserves key metadata; verifies source poses, protected channels and full-clip body connections. Optional stationary-foot contact stabilization. Checked outer transaction/rollback required.

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": {
      "character_id": "<character_id>",
      "keys": "<keys>"
    },
    "name": "character_retime"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYes
character_idYes
stabilize_contactsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior4/5

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

Beyond destructiveHint=true and readOnlyHint=false, it discloses metadata preservation, source-pose and protected-channel verification, full-clip connection checks, and the transaction/rollback prerequisite. It does not spell out exactly which target keys get overwritten or the rollback failure behavior, keeping it below exhaustive.

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?

The description is front-loaded and compact at four sentences, with no obvious filler. Some domain jargon such as authored Point targets and finger-local rotations is dense but still purposeful.

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?

For a destructive nested-key retiming tool with no output schema, it covers the transaction prerequisite and verification behavior, which are high-value. It is incomplete on several input semantics and sibling choice, so it is adequate rather than fully self-contained.

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?

With 0% schema description coverage, the description only partly compensates: it explains the 2-8 key count and stabilize_contacts, and broadly references Point targets/settings. It leaves character_id, left_weight/right_weight, and the interpolation enum unexplained, so an agent cannot confidently set those fields from the prose.

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 names a specific verb (retime), resource (character keys), and scope (2-8 synchronized keys), plus domain constraints like Point targets and finger-local rotations. It does not explicitly route against sibling tracks_retime, so it is strong but not fully sibling-differentiating.

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?

It supplies operational conditions such as 2-8 keys, optional contact stabilization, and a required checked outer transaction/rollback, which imply when the tool applies. However, it never states when to choose this over tracks_retime or other pose/key tools.

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

Deploy Server

Other Tools