Skip to main content
Glama

adb_firmware_history

Track firmware version progression across saved OTA fingerprints for a device, including baseband, bootloader, kernel, security patch, and build ID changes between snapshots.

Instructions

Show firmware version progression across all saved OTA fingerprints for a device. Tracks baseband, bootloader, kernel, security patch, and build ID changes between consecutive snapshots with parsed component diffs.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial (filters fingerprints to 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 behavioral burden. It discloses that results are derived from previously saved fingerprints and are expressed as parsed per-component diffs, which is useful, but says nothing about prerequisites (must fingerprints be captured first?), how fewer than two snapshots are handled, ordering, or whether the call is read-only.

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, with the core purpose front-loaded and the component list following as supporting detail. Every clause contributes and nothing is repeated from structured fields.

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 one-parameter read tool with no output schema, the description conveys what is compared and which components appear in the diffs. It leaves open prerequisites around saved fingerprints and the empty/insufficient-data case, which matter for correct invocation of a history-style tool.

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 coverage is 100% and the single 'device' parameter is fully documented, so the baseline is 3. The description only echoes the filtering idea with 'for a device' and adds no format, default, or behavior detail beyond the schema.

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?

Names a specific verb and resource: showing firmware version progression across saved OTA fingerprints, and enumerates the tracked components (baseband, bootloader, kernel, security patch, build ID). It is clearly a historical comparison tool rather than a probe, but it never explicitly distinguishes itself from near neighbors like adb_ota_history, adb_firmware_probe, or adb_firmware_diff.

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 implied by the phrasing 'across all saved OTA fingerprints' and 'between consecutive snapshots', which tells the agent this is for retrospective comparison rather than live probing. There is no explicit when-to-use statement, no exclusion, and no named alternative, so the agent must infer the choice among the OTA/firmware siblings.

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