Skip to main content
Glama

adb_ota_fingerprint

Capture and save the current Android system fingerprint (build ID, version, security patch, bootloader, firmware, kernel, A/B slot) to a timestamped JSON file for later OTA comparison.

Instructions

Capture and save the current system fingerprint: build ID, Android version, security patch, bootloader, baseband firmware, kernel version, and A/B partition slot. Saves to a timestamped JSON file for later comparison.

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

Input Schema

NameRequiredDescriptionDefault
labelNoLabel for this fingerprint (e.g., 'pre-update', 'post-ota')current
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

A3.6/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 does disclose the meaningful side effect (writes a timestamped JSON file to disk) and the captured field set, but omits where the file is written, whether a device must be connected/authorized, and whether the operation is purely read-only on the device.

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 action and field list, followed by the persistence outcome. Every clause carries information and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should indicate what the caller gets back; it states the artifact (timestamped JSON file) but not the file path or return payload. Given the tool's modest complexity and fully documented parameters, it is otherwise complete enough to call correctly.

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 'label' (default 'current', example values given) and 'device' (serial) documented in the schema itself. The description adds no meaning beyond that — it never mentions label semantics or the device serial — so the baseline 3 applies.

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+resource ('Capture and save the current system fingerprint') and enumerates exactly which fields are captured (build ID, Android version, security patch, bootloader, baseband, kernel, A/B slot). It does not name a sibling to distinguish itself from, e.g., adb_firmware_probe or adb_device_info, so an agent must infer the boundary itself.

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?

'Saves ... for later comparison' implies the pre-/post-OTA baseline workflow, and the schema's label example ('pre-update', 'post-ota') reinforces it. However, there is no explicit statement of when to prefer this over adb_firmware_probe, adb_snapshot_capture, or adb_getprop, and no prerequisites are given.

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