Skip to main content
Glama

adb_ota_check

Compare a device's current system state against a saved fingerprint to detect OTA updates by flagging changes in build ID, security patch, baseband, bootloader, or kernel version.

Instructions

Compare the current system state against a saved fingerprint. Detects OTA updates by identifying changes in build ID, security patch, baseband firmware, bootloader, or kernel version.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
fingerprintPathNoPath to saved fingerprint JSON. If omitted, compares against the most recent fingerprint for this device.

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
Behavior2/5

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

With no annotations, the description carries the full burden. It does not say whether the operation is read-only, what happens when no fingerprint exists for the device, whether a mismatch causes an error or a normal result, or how changes are reported. Only the comparison semantics are conveyed.

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 tight sentences with the action front-loaded and the detection criteria enumerated second. No filler, no restatement of the title, and every clause contributes information.

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 two-parameter tool with no output schema and no annotations, the description should say what the comparison returns (e.g., a verdict plus changed-field list) and what happens on a missing baseline fingerprint. Those gaps are real but modest given the tool's simplicity and the fully documented schema.

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% and both parameters (device serial, fingerprintPath with its default-to-most-recent behavior) are fully documented in the schema. The description adds no syntax, format, or fallback detail beyond that, so the baseline of 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?

States a concrete verb and resource: compare current system state against a saved fingerprint, and names the specific fields inspected (build ID, security patch, baseband, bootloader, kernel). It is clearly distinct from siblings like adb_ota_fingerprint (saving) and adb_ota_history, though it does not name those alternatives explicitly.

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?

Usage is only implied: you must have a saved fingerprint first, which the schema hints at but the description never states. There is no guidance on when to prefer this over adb_firmware_diff or adb_ota_history, nor any stated precondition such as 'run adb_ota_fingerprint first'.

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