Skip to main content
Glama

List Adb Devices

list_adb_devices
Idempotent

Lists attached Android devices with adb-style serial, state, transport, model metadata, and inferred emulator/physical type so you can identify targets before debugging or inspection.

Instructions

List attached devices exactly as adb devices -l reports them: serial, state, transport, model metadata, and an inferred emulator/physical kind with its evidence basis. Emulators and USB or network devices appear alike; REA neither starts nor manages them. May start the local adb server on first use.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_adb_devices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations say readOnlyHint=false, which is counterintuitive for a listing tool; the description resolves this by disclosing 'May start the local adb server on first use.' It also sets scope boundaries — REA neither starts nor manages the listed devices — and explains the inferred kind with an evidence basis, which is behavior not visible in the schema.

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?

Two compact sentences, front-loaded with the core action and equivalence, followed by output fields and scope caveats. No filler and no repetition of the name or title.

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?

With no input parameters and no output schema, the description carries the return-value burden itself and does so by naming the fields reported and the emulator/physical inference with its evidence basis. It also covers the side effect of starting the adb server, leaving nothing an agent needs before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning left to document and the description correctly spends no space on inputs, focusing instead on what the parameterless call returns.

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 ('List attached devices') and pins the exact semantics to `adb devices -l`, enumerating the returned fields (serial, state, transport, model metadata, inferred kind). It implicitly separates itself from deeper siblings like inspect_adb_device by framing this as the raw device listing, 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 Guidelines3/5

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

Usage is implied by the verb and the 'adb devices -l' equivalence, and it usefully notes that emulators and USB/network devices all appear alike. There is no explicit when-to-use vs. when-to-inspect-elsewhere guidance and no named alternative such as inspect_adb_device for per-device detail.

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