Skip to main content
Glama

adb_pair

Pair an Android device over WiFi using its IP address and pairing code to enable wireless ADB debugging without a USB connection.

Instructions

Pair with a device over WiFi using the pairing code from Developer Options → Wireless debugging → Pair 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": {
      "host": "<host>",
      "code": "<code>"
    },
    "name": "adb_pair"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes6-digit pairing code shown on the device
hostYesDevice IP and pairing port (e.g., '192.168.1.100:37123')

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 / host / pattern
      Added value: +"^(?:\\d{1,3}\\.\\d{1,3}\\.\\d{1,3}\\.\\d{1,3}|\\[[0-9a-fA-F:]+\\]|[a-zA-Z0-9][a-zA-Z0-9.-]*):\\d{1,5}$"
  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 supplied, so the description carries the full disclosure burden. It usefully explains that the code comes from the on-device pairing dialog, but it omits what pairing actually establishes, whether it persists, whether adb_connect is required afterward, and what failure looks like.

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?

A single front-loaded sentence with the action first and the code-location hint second. No filler, nothing to trim.

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?

For a two-parameter tool with full schema coverage and no output schema, the description covers the input side adequately. It is thin on outcome and follow-up (that a connect step is typically needed next), which matters for a trust-establishing operation.

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 are documented, including the regex-constrained host:port form and the 6-digit code format. The description adds no parameter meaning beyond pointing at where the code is displayed, so the baseline 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 specific verb and resource ('Pair with a device over WiFi') plus the exact source of the pairing code, which distinguishes it from adb_connect (connecting to an already-paired device) and adb_tcpip. It stops short of naming the sibling it complements, so the differentiation is inferable rather than explicit.

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?

The Developer Options → Wireless debugging → Pair device path implies this is the first step of wireless setup, but the description never states when to use this versus adb_connect or adb_tcpip, nor any prerequisites such as both devices being on the same network.

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