Skip to main content
Glama

adb_snapshot_compare

Compare an Android device's current state with a saved snapshot to identify added or removed packages, changed settings, and property differences.

Instructions

Compare current device state against a saved snapshot. Shows added/removed packages, changed settings, and property differences.

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_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
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
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the categories of output (packages, settings, properties), but never states that the operation is read-only/non-mutating, what happens if the snapshot file is missing or stale, or whether comparison is exact-match or tolerant.

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 with zero filler: the comparison action is front-loaded, and the second sentence efficiently enumerates the output categories. Nothing is repeated from the schema or wasted.

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 simple two-parameter tool this covers purpose and rough output shape, but with no annotations and no output schema the description should have disclosed that it is non-destructive, the prerequisite of a valid snapshot file, and any error behavior. Those gaps leave the agent underinformed about safe invocation.

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 both 'device' (Device serial) and 'snapshotPath' (Path to the saved snapshot JSON file) documented in the schema. The description adds no parameter-level detail such as path format or device-selection behavior, so the baseline of 3 applies.

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 names a specific verb (Compare) and resource (current device state vs a saved snapshot), and scopes the result to added/removed packages, changed settings, and property differences. That scope distinguishes it from sibling comparison tools such as adb_thermal_compare or adb_firmware_diff without needing to open their schemas.

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 phrase 'against a saved snapshot' implies the prerequisite that a snapshot must already exist, but the description never names adb_snapshot_capture as the source, gives no when-not guidance, and offers no alternatives for broader regression checks (e.g., adb_regression_check). Usage is implied rather than stated.

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