Skip to main content
Glama

adb_gps_firmware

Identifies GNSS/GPS chipset and firmware details on Android devices, reporting hardware model, constellations, frequencies, and A-GPS modes for spoofing and IMSI catcher research.

Instructions

GNSS/GPS chipset and firmware identification. Reports GNSS hardware model (manufacturer, chip, firmware version), supported constellations (GPS, GLONASS, Galileo, BeiDou, QZSS, NavIC, SBAS), signal types with frequencies, dual-frequency (L1+L5) support, raw measurement capabilities (pseudorange access for spoofing detection), A-GPS modes (MSB/MSA — cellular-routed assisted GPS relevant to IMSI catcher research), carrier phase measurements, navigation message decoding, and SUPL server configuration.

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

Input Schema

NameRequiredDescriptionDefault
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.1/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 behavioral burden, and it does disclose a rich set of returned attributes (constellations, frequencies, A-GPS modes, carrier phase, SUPL config), which implies a passive read. It never explicitly states read-only semantics, whether root/privileged access is needed, or what happens on devices with no GNSS hardware.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, which is good, but the remainder is a long comma-separated enumeration of reportable fields that reads as a feature dump rather than prioritized guidance. Most items are informative, though parenthetical asides like the IMSI-catcher note add length without helping invocation.

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?

With no output schema, the description correctly compensates by describing return contents in detail, which is the main completeness requirement here. It is still missing invocation-relevant context: how it differs from sibling probe tools and any device/privilege constraints, leaving gaps for a tool in a very crowded firmware/telephony family.

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?

There is a single optional 'device' parameter and schema description coverage is 100%, so the schema already fully documents it. The description adds nothing about the parameter (e.g., defaulting to the single connected device), so 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 opens with a specific verb+resource pair ('GNSS/GPS chipset and firmware identification') and then enumerates exactly what is reported, so an agent knows this is a read-only probe of GNSS hardware/firmware. It does not, however, distinguish itself from related siblings such as adb_firmware_probe, adb_baseband_info, or adb_wifi_firmware.

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 at all: nothing says when to reach for this instead of adb_firmware_probe, adb_baseband_info, adb_location, or adb_signal_detail, nor are prerequisites or failure conditions mentioned. The agent must infer usage purely from the tool name.

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