Skip to main content
Glama

adb_bluetooth_firmware

Identify Bluetooth firmware and chipset details, including BT version, adapter state, supported profiles, LE capabilities, and bonded device count; include identifiers only on request.

Instructions

Bluetooth firmware and chipset identification. Reports firmware version, BT version (4.x/5.x), chipset model, adapter state, supported profiles, LE capabilities, and bonded device count. MAC address and device name are opt-in only (permanent identifiers).

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
maxLinesNoLines of dumpsys output to inspect (50-2000, default 300). Raise for verbose vendor builds.
includeIdentifiersNoInclude Bluetooth MAC address and device name (permanent identifiers — 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": 300,
      +  "description": "Lines of dumpsys output to inspect (50-2000, default 300). Raise for verbose vendor builds.",
      +  "maximum": 2000,
      +  "minimum": 50,
      +  "type": "integer"
      +}
  3. First observedv1.1.1

TDQS

A3.8/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 well to disclose the sensitive-identifier handling ('MAC address and device name are opt-in only') and implies a read-only probe by using 'Reports', but never states whether Bluetooth must be enabled, whether privileged/root access is required, or what happens on failure.

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?

Three short sentences, zero filler, with the capability list front-loaded and the privacy caveat placed last where it belongs. Every sentence contributes something an agent would otherwise have to guess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the enumeration of returned fields substitutes well and tells the agent what it will get back. Three all-optional parameters keep the call surface simple; the only real gap is preconditions (adapter off, permission requirements) for a probe that reads dumpsys-level state.

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%, including the maxLines range/default and the includeIdentifiers privacy note, so the schema already does this work. The description restates the identifier opt-in rule but adds nothing about when to raise maxLines or what device selection means.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (Bluetooth firmware and chipset) and enumerates exactly what is reported: firmware version, BT version, chipset model, adapter state, profiles, LE capabilities, bonded device count. The Bluetooth qualifier cleanly separates it from the analogous siblings adb_wifi_firmware, adb_nfc_firmware, adb_gps_firmware and adb_firmware_probe without needing to name them.

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 context is only implied by the content of the report; there is no explicit 'use this when you need X, use adb_firmware_probe instead when you need Y'. The opt-in identifier note is a useful conditional but is a privacy rule, not a when-to-use rule.

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