Skip to main content
Glama

Snapshot device

device_snapshot

Save a running device's disk (installed apps, logins, settings) as a snapshot. Returns it as pending; it becomes ready shortly. Snapshots are stored durably and can be restored on any host: device_restore boots a new device from it.

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": {
      "device_id": "<device_id>"
    },
    "name": "device_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
device_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the return is asynchronous ('pending; it becomes ready shortly'), that storage is durable, and that the artifact is portable across hosts. It omits permissions/auth requirements and whether the source device keeps running, which keeps it from a 5.

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?

Three short sentences, front-loaded with the core action, then the async lifecycle, then the restore path. Every sentence adds information; nothing is padded.

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?

No output schema and no annotations, so the description is the only source, and it explains the pending→ready lifecycle but not how to check readiness (e.g., whether to poll device_list or task_status) or what identifier is returned. The `name` parameter is left entirely unexplained.

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 description coverage is 0%, so the description must compensate, and it does not: the optional `name` parameter is never mentioned, and `device_id` is only implied by 'a running device's disk'. An agent gets no guidance on naming conventions or the 64-character limit.

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 ('Save a running device's disk ... as a snapshot') and even enumerates what the snapshot captures (installed apps, logins, settings). It also names the sibling it pairs with (device_restore), so an agent can distinguish it from device_screenshot or device_create without opening a schema.

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

Usage Guidelines4/5

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

Usage context is clear: snapshot when you want durable state that can later be booted on any host via device_restore. The phrase 'running device's disk' implies the device must be started first. There are no explicit exclusions or 'do not use when' clauses, so it stops short of a 5.

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