Skip to main content
Glama

Scene Rollback

scene_rollback

Restore a Maya scene from a checkpoint and rebind it to its original path, while saving current state to a safety snapshot first; abort if that snapshot fails unless discarded.

Instructions

Open a checkpoint and rebind the scene to its original path (S2).

Boundary: Disambiguated from scene_checkpoint (write a checkpoint from the current state) and scene_checkpoint_list (enumerate the ones already written) — scene_rollback is the restore half.

Before opening, the current in-memory state is exported to an auto_before_rollback safety snapshot; if that fails, the rollback aborts — pass discard_current_state=True to escape (the result reports safety_snapshot="skipped_by_user"). Untitled scenes and ad-hoc snapshots have no original path, so the scene stays on the checkpoint path (S1) and scene_rebound_to is null.

The snapshot carries no undo history — call scene_snapshot afterwards to rebuild context.

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": {
      "filename": "<filename>"
    },
    "name": "scene_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesCheckpoint filename from scene_checkpoint_list (cp_*.ma or prev_*.ma).
session_keyNoMaya session key.
discard_current_stateNoEscape hatch — proceed even if the safety snapshot fails.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.8/5.0
Behavior5/5

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

Well beyond the annotations: discloses the auto_before_rollback safety snapshot, the abort-on-snapshot-failure behavior, the skipped_by_user result value, the null scene_rebound_to outcome for untitled scenes, and the absence of undo history. That is exactly the destructive-side-effect context an agent needs before invoking a restore.

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?

Front-loaded with the action, then a boundary line, then prerequisites and follow-ups in a logical order; every sentence carries information. Minor cost: the unexplained "(S2)"/"(S1)" tags add jargon without adding meaning for an outside caller.

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

Completeness5/5

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

Given an output schema exists, the description needn't document return shape, and it still names key result fields. It covers preconditions, failure modes, edge cases, and post-call guidance, which is complete for a restore operation.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning beyond the schema: it explains the consequence of discard_current_state (proceed despite failed snapshot) and the resulting safety_snapshot="skipped_by_user" value, and it ties filename to checkpoints produced by scene_checkpoint_list. session_key is left to the schema alone.

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

Purpose5/5

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

States a specific verb and resource ("Open a checkpoint and rebind the scene to its original path") and immediately delimits it against scene_checkpoint (write) and scene_checkpoint_list (enumerate), calling itself "the restore half." An agent can pick this over its siblings without opening any schema.

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

Usage Guidelines5/5

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

Explicit when-to-use routing against two named alternatives, plus an explicit escape-hatch condition ("pass discard_current_state=True to escape") and a follow-up recommendation ("call scene_snapshot afterwards to rebuild context"). Edge cases (untitled scenes, ad-hoc snapshots) are called out as cases where the tool still runs but scene_rebound_to is null.

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