Skip to main content
Glama

adb_snapshot_restore_settings

Restore global and secure Android settings from a saved snapshot to the current device, without installing or uninstalling packages.

Instructions

Restore settings from a saved snapshot to the current device. Only restores global and secure settings — does not install/uninstall packages.

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": {
      "snapshotPath": "<snapshotPath>"
    },
    "name": "adb_snapshot_restore_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
namespaceNoWhich settings namespace to restoreboth
snapshotPathYesPath to the saved snapshot JSON file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden, and it does disclose the most important trait: this is a mutating overwrite limited to global and secure namespaces, and it will not touch packages. That tells an agent what state is at risk. What is missing is whether the restore is wholesale or key-by-key, and whether elevated permissions such as WRITE_SECURE_SETTINGS are required.

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 sentences, no filler, and the core action is front-loaded ahead of the scope caveat. Every clause earns its place by either defining the operation or bounding it.

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?

For a three-parameter mutation tool with no annotations and no output schema, the description covers purpose and scope but leaves gaps an agent would want: permission requirements, failure behavior on malformed or partial snapshots, and the capture-then-restore workflow relationship. It is adequate but not complete.

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 description coverage is 100%, with all three parameters documented including the global/secure/both enum, so the baseline is 3. The description confirms that global and secure are the only meaningful namespaces, but adds no semantics for snapshotPath format or the device serial beyond what the schema already provides.

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: 'Restore settings from a saved snapshot to the current device.' This is clearly distinguishable from the sibling snapshot tools adb_snapshot_capture and adb_snapshot_compare, though those siblings are never named, so the differentiation is inferable rather than explicit.

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 second sentence bounds the operation to global and secure settings and excludes package install/uninstall, which gives useful context about what this tool will and will not do. However, it never says when to prefer it over adb_settings_put for individual keys, nor does it state the prerequisite of having a snapshot produced by adb_snapshot_capture.

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