mcp-for-cascadeur

Overview Schema Source Related Servers Discussions Admin

pose_restore

Destructive

Restore a saved pose snapshot after validating the scene path and topology, while accounting for interpolation and solver effects on neighboring frames.

Instructions

Restore a pose snapshot after checking saved scene path and topology. Native interpolation and solvers can affect neighboring frames.

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": "pose_restore"
  }
}

Input Schema

Name	Required	Description
`path`	No
`frame`	No
`verify`	No
`snapshot_id`	No
`position_tolerance`	No	Accepted native position readback error in scene units; does not alter writes.
`rotation_tolerance`	No	Accepted native quaternion angular error in radians; does not alter writes.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 7, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds a genuinely non-obvious side effect: native interpolation and solvers can alter neighboring frames, widening the blast radius beyond the restored pose. It still omits what happens to the current pose and whether the snapshot survives the restore, so it is not fully complete.

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?

Two short sentences with the operation front-loaded and no filler. The precondition clause is somewhat compressed to the point of being cryptic, but nothing is wasted.

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, 6-parameter mutation with no output schema and zero required parameters, the definition leaves key gaps: it never explains how the target snapshot is selected, what the pre-check actually validates, or what the call returns on failure. The neighboring-frame warning is valuable but does not cover the selection mechanics.

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?

Schema description coverage is only 33% (tolerances only), so the description must compensate for path, frame, verify and snapshot_id — and it largely does not. The mention of 'saved scene path' vaguely gestures at the path parameter but leaves the critical ambiguity unresolved: how a snapshot is identified (snapshot_id vs path vs frame), and what 'verify' does.

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 resource ('Restore a pose snapshot'), so the core operation is unambiguous. However, among ~70 siblings there are several near-identical restore tools (character_pose_restore, subtree_restore, checkpoint_restore, recovery_restore) and the description never says how pose_restore differs from them.

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?

'After checking saved scene path and topology' implies a precondition but never states it operationally or says when to choose this over pose_apply / character_pose_restore / checkpoint_restore. Usage is only inferable, not explicit.

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

Deploy Server