Skip to main content
Glama

adb_multi_compare

Compare outputs from the same shell command across Android devices side by side, highlighting differences for cross-device diagnostics.

Instructions

Run a command on all devices and compare outputs side by side. Highlights differences across devices.

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

Input Schema

NameRequiredDescriptionDefault
commandYesShell command to compare across devices
devicesNoDevice serials (omit for all online devices)

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

B3.3/5.0
Behavior2/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, yet it discloses only the fan-out-and-diff shape. It says nothing about how partial failures (offline or unauthorized devices) are reported, whether execution is parallel or sequential, whether the arbitrary shell command is treated as read-only or potentially destructive, or how the 'highlighted differences' are formatted in the response.

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 short sentences with the action and its result front-loaded and no filler. It is efficient, though the second sentence largely restates the comparison already implied by 'compare outputs side by side'.

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?

For a two-parameter tool with a fully documented schema and no output schema, the description conveys the essential contract: one command, many devices, diffed results. The gap is behavioral rather than structural — error semantics and output shape of the comparison are unstated, which matters more here because there are no annotations to fall back on.

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%, so both the command and devices parameters are already documented, including the useful note that omitting devices targets all online devices. The description adds no syntax, quoting, or safety guidance for the command string and does not mention the devices subsetting at all, so the baseline of 3 applies.

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 concrete verb pair ('run a command', 'compare outputs') against a clear scope ('all devices'), plus the outcome ('highlights differences'). An agent can distinguish it from adb_shell or adb_multi_shell by the comparison framing, but the description never names those siblings, so differentiation is inferred rather than stated.

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 only implied: the comparison framing suggests you call it when you want cross-device output diffs. There is no explicit when-not guidance, no mention of the closely related adb_multi_shell (fan-out without diffing) or adb_multi_test, and no stated preconditions such as devices needing to be online.

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