Skip to main content
Glama

adb_ota_history

List saved system fingerprints for a device to track Android version progression over time and highlight changes between consecutive OTA snapshots.

Instructions

List all saved system fingerprints for a device, showing version progression over time. Highlights changes between consecutive snapshots.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial (filters to this device). Omit for all devices.

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.5/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 something about the output shape (progression over time, and that consecutive-snapshot changes are highlighted), which is genuinely useful, but it never states that this is a non-destructive read, how results are ordered or bounded, or what an empty history looks like.

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 short sentences, front-loaded with the core action and followed by the value-add about change highlighting. There is no filler or restated naming, and each sentence contributes distinct 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 one-parameter, non-destructive listing tool with no output schema, the description covers the gist but leaves the return structure underspecified — an agent knows it gets versions and diffs but not the fields, ordering, or how many snapshots are retained. With no annotations and no output schema, a sentence on the result shape would have closed the gap.

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 the single `device` parameter is already documented in the schema, including the omit-for-all-devices behavior. The description's "for a device" adds only faint reinforcement, 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?

The description states a specific verb and resource ("List all saved system fingerprints for a device") and adds the temporal dimension ("version progression over time"), which distinguishes it from a capture-style sibling like adb_ota_fingerprint. It does not, however, explicitly name or rule out the nearest alternatives (adb_firmware_history, adb_ota_check), so the differentiation is implicit rather than stated.

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 word "saved" and "over time" imply this is the retrieval/history tool rather than a fresh capture, so usage is inferable. But there is no explicit when-to-use or when-not-to-use guidance, and no pointer to adb_ota_fingerprint (capture) or adb_firmware_diff/history as the natural alternatives for an agent choosing among them.

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