Skip to main content
Glama

adb_multi_shell

Run an ADB shell command across multiple or all connected Android devices in parallel, with results grouped by device.

Instructions

Execute a shell command on multiple (or all) connected devices in parallel. Returns results grouped by device.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command": "<command>"
    },
    "name": "adb_multi_shell"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYesShell command to execute on each device
devicesNoDevice serials to target (omit for all online devices)
timeoutNoTimeout per device in milliseconds (1s-10min)

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

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

No annotations are provided, so the description carries the full burden. It adds two useful behaviors: execution is parallel and results are grouped by device. It is silent on partial-failure semantics (does one device's failure abort the rest?), whether results are ordered, and whether the command runs with elevated or normal shell privileges.

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 short sentences: the action and scope first, the return-shape note second. No filler, no redundancy, and the most decision-relevant fact (parallel, multi-device) is front-loaded.

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 annotations and no output schema, the description does just enough: it states the return grouping so the agent knows results are per-device rather than merged. It is still thin for an unannotated tool that runs arbitrary shell commands across a fleet, omitting failure behavior and any safety or authorization context.

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 all three parameters, including the per-device timeout range, are already documented in structured data. The description only reinforces the devices-omitted-means-all behavior already stated in the schema, adding no syntax or format detail.

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 names a specific verb+resource ("Execute a shell command") and adds a differentiating scope qualifier: on multiple or all devices, in parallel. That scope distinction separates it from adb_shell without requiring the agent to open a schema, though it never names that sibling 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?

"On multiple (or all) connected devices" implies the multi-device use case, and the schema's devices description notes omitting it targets all online devices. However, there is no explicit guidance on when to prefer this over adb_shell looped per device, nor on preconditions such as needing more than one connected device.

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