Skip to main content
Glama

Restore snapshot

device_restore

Boot a NEW device from a ready snapshot (the original device is untouched). Omit snapshot_id to list snapshots.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
waitNoWait until booted, up to 25 s
snapshot_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description does real work by disclosing that a new device is created and the original is left intact — a non-destructive guarantee an agent could not otherwise assume. It omits what the new device inherits, whether the call is idempotent, and what the tool returns in each of its two modes.

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 sentences, both load-bearing: the first defines the operation and its safety property, the second delivers the one non-obvious usage rule. No filler.

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?

The core behavior is covered, but with no output schema and no annotations, the description should say what comes back — a new device identifier, and a different shape when snapshots are listed. That gap matters more for a tool with a dual mode than it would for a simple read.

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?

Schema coverage is only 33% (just `wait`), so the description must compensate; it does so well for `snapshot_id` by revealing that omitting it flips the tool into a list mode, which the schema does not say. The `name` parameter goes entirely undocumented in both places, leaving the compensation incomplete.

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+resource combo ("boot a NEW device from a ready snapshot") and clarifies the non-obvious semantics that the source device is untouched. It is distinguishable from device_start and device_snapshot, though it never names device_create as the alternative.

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?

The clause "Omit snapshot_id to list snapshots" gives one actionable usage rule, and "ready snapshot" implies a prerequisite. But there is no guidance on when to restore from a snapshot versus calling device_create or device_snapshot, so the when-to-use decision is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources