Skip to main content
Glama

adb_snapshot_capture

Capture an Android device’s installed packages, key settings, and system properties into a JSON snapshot for inspection, comparison, or troubleshooting.

Instructions

Capture a comprehensive device state snapshot: installed packages, key settings, and system properties. Saves to a JSON file.

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

Input Schema

NameRequiredDescriptionDefault
nameNoSnapshot name (default: auto-generated timestamp)
deviceNoDevice serial

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

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses that the result is persisted to a JSON file and what categories of state are collected. However, it omits the file path/location, whether device-side privileges are required, whether the operation is purely read-only, and how failures are surfaced – all material for a snapshot tool whose output is consumed by sibling compare/restore tools.

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, front-loaded with the verb and content before the persistence detail; no filler or redundancy. 'Comprehensive' is slightly promotional but does not undermine clarity.

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 zero-required-parameter tool, the core purpose and persistence behavior are covered. But with no output schema and no annotations, the description should state where the JSON is written or what the tool returns, since sibling tools like adb_snapshot_compare and adb_snapshot_restore_settings presumably need to reference that artifact.

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%, so the 'name' (default auto timestamp) and 'device' parameters are already fully documented. The description adds no further parameter semantics beyond the implicit connection between naming and the saved JSON file, which is the expected baseline.

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?

The description gives a specific verb ('Capture') and resource ('device state snapshot') and enumerates the captured content (packages, settings, system properties), so the agent knows exactly what the tool produces. It does not explicitly differentiate from siblings such as adb_snapshot_compare or adb_profile_save, leaving the routing distinction implicit.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (connected device, root, USB debugging), and no reference to alternatives or follow-up tools like adb_snapshot_compare. The agent must infer from the name that this is a baseline-capture step.

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