Skip to main content
Glama

Restore a snapshot

restore_snapshot
Destructive

Restore a snapshot to its source computer, overwriting the current disk and discarding changes since capture. Check restore availability first; orphaned snapshots require cloning instead.

Instructions

Put a snapshot back onto the computer it came from, discarding everything on that disk since. Check restore_available in list_snapshots first: where it is false, the snapshot's usable copy is on a host its computer has left, and a restore is refused while clone_snapshot still works. Refused on an orphaned snapshot — clone_snapshot is what works there. It leaves the computer RUNNING whatever state it was in: restoring a stopped one boots it, which is a start like any other and consumes running capacity. A disk snapshot comes back to a fresh boot, a memory one to the captured session, and either way a suspended session the computer was holding is discarded with the disk it was saved against.

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": {
      "snapshot_id": "<snapshot_id>",
      "confirm": "<confirm>"
    },
    "name": "restore_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. This overwrites the source computer's current disk.
snapshot_idYes
idempotency_keyNoOptional. Omit it on a first attempt: a fresh key is sent for you, and an answer that is lost names it. Pass the key such an answer named to send the SAME call again without it being done twice — the platform answers with the first call's result, or says it is still running. After a 5xx that names no operation_id, send the same call again with the same key: nothing may have been done, and the platform either carries it out (the key was released) or answers idempotency_outcome_unknown. After idempotency_outcome_unknown, or a 5xx that names an operation_id, the key is spent (resending with it answers idempotency_outcome_unknown), and the call may still be under way: read its operation first (get_operation with the operation_id the error named, or list_operations with the key), wait while it is pending or running and do not resend meanwhile, and send the call with a new key (or none) only once the operation is final as failed or not found AND get_computer shows the step did not happen. Keys last 24 hours; the same key with different arguments is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.1

TDQS

A4.6/5.0
Behavior5/5

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

Although destructiveHint=true already warns of destruction, the description adds materially: it says everything on the disk since the snapshot is discarded, defines refusal conditions, and explains that the computer is left running and may consume running capacity if a stopped one is booted. It also discloses disk-vs-memory snapshot behavior and that a held suspended session is discarded.

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 with the core action and then layers preconditions and side effects in a logical order. It is dense and useful, but the orphaned-snapshot/clone_snapshot point is repeated in slightly different words, costing some conciseness.

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?

For a destructive, state-changing restore operation, the description covers legality checks, refusal alternatives, disk and memory outcomes, and running-capacity side effects. Since no output schema exists and idempotency details are carried by the schema, the remaining omissions are not material.

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

Parameters3/5

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

The schema describes confirm and idempotency_key, but snapshot_id has no schema description. The prose implies snapshot_id is a snapshot tied to the originating computer but adds no format, lookup, or idempotency detail beyond what the schema already provides, so with 67% schema coverage this is minimally adequate.

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?

The description states a specific verb and resource — putting a snapshot back onto its source computer — and makes clear it overwrites changes since the snapshot. It also distinguishes the operation from clone_snapshot and list_snapshots, so an agent can identify it without reading sibling schemas.

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?

It gives an explicit pre-check: inspect restore_available in list_snapshots first. It then spells out what to do when restore is refused, including the orphaned-snapshot case and the fact that clone_snapshot is the working alternative.

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