Skip to main content
Glama
Blender Production MCP

Blender Production MCP

by DiegoArias32

production.animation_restore_action

Reassign a preserved animation action using a checkpoint without deleting the current action, so production workflows can restore prior animation safely.

Instructions

Reassign a preserved Action with checkpoint; never delete the current Action.

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": {
      "object_name": "<object_name>",
      "action_name": "<action_name>"
    },
    "name": "production.animation_restore_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
action_nameYes
object_nameYes
operation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare non-destructive and non-idempotent, and the description adds one useful guarantee (current Action is preserved). However, it omits the critical behavioral default that dry_run=true, meaning a naive call performs no restore — a major transparency gap for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no wasted padding, but it front-loads an ambiguous verb rather than the concrete operation and scope. Brevity here is under-specification rather than efficiency.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating 4-parameter tool with zero schema descriptions, the definition leaves out the dry_run default, the meaning of operation_id, and any notion of what state changes on a real run. An output schema exists so return values need no explanation, but the input-side gaps remain serious.

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

Parameters1/5

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

Schema description coverage is 0% and the description adds no parameter meaning at all. It never explains what action_name vs object_name identify, what operation_id is for, or that dry_run defaults to true and must be turned off to actually reassign.

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?

"Reassign a preserved Action with checkpoint" conveys a restore-like operation on an Action resource, but "Reassign" is ambiguous and the phrase does not clearly differentiate this from siblings like animation_duplicate_action or restore_checkpoint. The second clause clarifies scope (never delete the current Action) but not the core action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to use this versus animation_duplicate_action, animation_create_action, or the checkpoint tools, and no prerequisites or exclusions. The only guidance is a negative constraint ("never delete the current Action"), not a usage condition.

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