Skip to main content
Glama

adb_at_cross_validate

Cross-validate baseband firmware by comparing modem AT command responses with Android system properties to detect tampering, incomplete OTA updates, or property spoofing. Requires root.

Instructions

Cross-validate baseband firmware by comparing AT command responses (direct modem interrogation) against Android system properties (getprop). Discrepancies may indicate firmware tampering, incomplete OTA updates, or property spoofing. Sends ATI (identification), AT+CGMR (firmware revision), and AT+CGMM (model) to the modem and compares with gsm.version.baseband, ro.hardware.chipname, and related properties. Requires root.

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

Input Schema

NameRequiredDescriptionDefault
portNoModem device node (auto-detects if omitted)
deviceNoDevice serial
timeoutNoResponse timeout per command in ms

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.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and handles most of it: it discloses the root requirement, the exact modem commands issued, the properties read, and that a per-command timeout applies. It implicitly conveys this is a read/compare operation with no mutation. What it omits is failure behavior (no modem node found, non-root, AT non-responsive) and whether the two sources are queried sequentially.

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?

Four tight sentences: purpose first, then interpretation of results, then the concrete mechanism, then the prerequisite. Every sentence contributes information and nothing is repeated from the schema or title.

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 moderately complex, root-requiring cross-validation tool with no output schema, the description explains inputs and mechanism well but never describes what comes back — no mention of a per-field comparison result, a mismatch report, or a verdict flag. An agent knows what the tool does but not what to expect in the response, and it lacks guidance on partial failures.

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%, so port, device, and timeout are already fully documented in the schema, including the auto-detect default for port and the 1000-30000 ms bounds for timeout. The description adds no parameter-level detail beyond that, which is acceptable but not additive. Baseline 3 applies when the schema does the heavy lifting.

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 ('Cross-validate baseband firmware') and explains the mechanism: comparing AT command responses against Android system properties. It names the exact AT commands (ATI, AT+CGMR, AT+CGMM) and properties (gsm.version.baseband, ro.hardware.chipname), which makes the purpose unmistakable. It stops short of naming siblings like adb_baseband_info or adb_at_send, so an agent must infer the distinction from the description alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for when this tool is appropriate by explaining what discrepancies indicate (firmware tampering, incomplete OTA updates, property spoofing) — that is the use case. It also states a hard prerequisite ('Requires root'). However, there are no exclusions and no explicit routing to alternatives such as adb_at_probe for single-command interrogation or adb_firmware_probe for broader firmware inspection.

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