Skip to main content
Glama

adb_wifi_firmware

Reports WiFi chipset, driver/firmware versions, supported bands/standards, interface details, connection state, and dumpsys excerpts from Android devices via ADB; MAC is opt-in.

Instructions

WiFi chipset and firmware identification. Reports WiFi driver version, firmware version, chipset/hardware info, supported bands and standards, interface details, and dumpsys excerpts. BH7 fix: dumpsys truncation now configurable via maxLines. connection state. MAC address is opt-in only (permanent hardware identifier).

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
maxLinesNoLines of dumpsys output to inspect (50-2000, default 200). Raise for verbose vendor builds where firmware info appears late in dumpsys output.
includeMacNoInclude WiFi MAC address (permanent hardware identifier — opt-in only)

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. Changed2 schema fields changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / maxLines
      Added value: +{
      +  "default": 200,
      +  "description": "Lines of dumpsys output to inspect (50-2000, default 200). Raise for verbose vendor builds where firmware info appears late in dumpsys output.",
      +  "maximum": 2000,
      +  "minimum": 50,
      +  "type": "integer"
      +}
  3. First observedv1.1.1

TDQS

C2.9/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 burden. It does disclose two genuinely useful traits: the operation is a reporting/read-style probe, and the MAC address is a permanent hardware identifier exposed only on opt-in, plus a note that dumpsys output is truncated by maxLines. It never states permissions, side effects, or failure behavior when the device is offline.

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

Conciseness2/5

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

The text is fragmented: the dangling sentence 'connection state.' has no subject, and 'BH7 fix: dumpsys truncation now configurable via maxLines' is an internal changelog line that occupies prime space. The scope enumeration is front-loaded, but the leftover fragments and fix note waste attention.

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 and no annotations, the description usefully enumerates the returned fields and flags the MAC privacy trade-off, which covers most of what an agent needs for a 3-parameter probe. It is still missing when-to-use routing and any statement of failure or permission conditions.

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 device, maxLines, and includeMac are already fully documented. The description only restates the MAC opt-in caveat and alludes to dumpsys truncation, adding little beyond the schema's own 'raise for verbose vendor builds' note. 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 first sentence names a specific resource and action (WiFi chipset and firmware identification) and the second enumerates exactly what is reported: driver version, firmware version, chipset/hardware info, bands, standards, interface details, dumpsys excerpts. That enumeration separates it in spirit from adb_wifi, adb_baseband_info, and adb_bluetooth_firmware, though no sibling is named explicitly.

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 statement of when to choose this over adb_wifi, adb_firmware_probe, adb_baseband_info, or adb_device_info, and no prerequisites or exclusions. The only directive is that MAC is opt-in, which is a privacy constraint on one parameter rather than routing guidance.

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