Skip to main content
Glama

restore_checkpoint

Load a saved revision into a remote Blender session, replacing the live scene; save current edits first to prevent losing unsaved work.

Instructions

Replace the live scene with a saved revision. Save current edits first.

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": {
      "session_id": "<session_id>",
      "revision": "<revision>"
    },
    "name": "restore_checkpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the key behavior: it replaces live scene state, and unsaved edits are at risk. It does not say whether the restore is reversible, whether an active session is required, or what happens with an invalid/stale revision—significant gaps for a destructive mutation.

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?

Two short front-loaded sentences, with the destructive action stated first and the safety prerequisite second. Every sentence earns its place with no filler.

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 destructive, irreversible-looking scene mutation with zero annotation coverage, two undocumented required parameters, and no output schema, the description is thin. It should explain session scoping, what a revision identifier looks like, and the consequences of failure.

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 coverage is 0% for both required parameters, so the description must compensate and largely doesn't. "Saved revision" loosely gestures at the revision parameter, but session_id is never mentioned and no formats, identifiers, or valid-value hints are given for either.

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: "Replace the live scene with a saved revision." It's clear this is a state-restoring operation on the active scene, distinguishable from list_checkpoints or save_project, though it doesn't explicitly name a sibling to route the agent.

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?

"Save current edits first" is an implied prerequisite that tells the agent this is destructive to unsaved work, which is real usage guidance. But it never states when to prefer this over alternatives (e.g., finding the revision via list_checkpoints, or opening a project), leaving selection between siblings to inference.

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