Skip to main content
Glama

adb_nfc_firmware

Identify NFC controller firmware on an Android device, reporting controller type, firmware and NCI versions, supported NFC technologies, secure element availability, and HCE support.

Instructions

NFC controller firmware identification. Reports controller type (NXP/Broadcom/Samsung/ST), firmware version, NCI version, supported technologies (NFC-A/B/F/V), secure element availability (eSE/UICC), and HCE (Host Card Emulation) support.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
maxLinesNoLines of dumpsys output to inspect (50-2000, default 200). Raise for verbose vendor builds.

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.",
      +  "maximum": 2000,
      +  "minimum": 50,
      +  "type": "integer"
      +}
  3. First observedv1.1.1

TDQS

B3.4/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 burden. It clearly discloses the returned content (controller vendor, firmware/NCI version, RF technologies, eSE/UICC, HCE), which implies a read-only identification operation, but says nothing about required permissions, whether it depends on dumpsys availability, or what happens on devices without NFC hardware.

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

Conciseness4/5

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

Two sentences, front-loaded with the identification purpose followed by the reported fields. No filler, though the long parenthetical enumeration is dense and could be trimmed without loss.

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

Completeness5/5

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

For a simple read-only probe with two well-documented parameters and no output schema, the description's enumeration of return fields effectively substitutes for the missing output schema. Nothing an agent needs to call it correctly is absent, aside from optional usage routing.

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 coverage is 100% and both parameters (device serial, maxLines with range and default) are fully documented in the schema. The description adds nothing about either parameter, so baseline 3 applies; it neither compensates nor misleads.

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?

States a specific verb and resource: "NFC controller firmware identification" plus an explicit enumeration of what is reported. This distinguishes it from the other firmware siblings (adb_wifi_firmware, adb_bluetooth_firmware, adb_gps_firmware) by resource, though it never names them or adb_firmware_probe.

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, no prerequisites, and no routing to alternatives such as adb_firmware_probe, adb_firmware_diff, or adb_firmware_history. The only cue is the resource name itself, which leaves the agent to infer that this is the NFC-specific firmware read.

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