Skip to main content
Glama

android_pair

Destructive

Pairs an authorized Android 11+ phone using its six-digit Wireless debugging code and pairing address so you can establish ADB access; then connect with the separate connection address.

Instructions

Pair a user-authorized Android 11+ phone using the current six-digit Wireless debugging code and PAIRING address. The connection address usually has a different port. Never guess codes. Then use android_connect.

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": {
      "address": "<address>",
      "code": "<code>"
    },
    "name": "android_pair"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.3

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is clear from structured data. The description adds genuinely useful behavior context – the pairing address usually differs in port from the connection address, and codes must come from the user's device rather than being fabricated. It does not address failure modes, code expiry, or retry behavior for this non-idempotent operation.

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?

Three short sentences, front-loaded with the action and inputs, then the address nuance, then the next-step pointer. No redundant restatement of the name or title.

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 pairing operation with annotations covering safety and no output schema, the description covers which address to use, where the code comes from, and what to call next. Remaining gaps – what a failed pair looks like and whether the code expires – are minor but would help.

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?

Schema coverage is 0%, so the description must carry the burden, and it does add real meaning: 'code' is the current six-digit Wireless debugging code (not any PIN), and 'address' is the PAIRING address, explicitly flagged as usually having a different port than the connection address. That disambiguation is essential and absent from the schema. Still no mention of address format or IPv6 bracket support.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (pair) and resource (a user-authorized Android 11+ phone) plus the required inputs (six-digit Wireless debugging code and PAIRING address). It also names android_connect as the follow-up step, so an agent can distinguish this tool from the sibling used to establish the actual connection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear context: use this first with the pairing code, then use android_connect. The warning 'Never guess codes' sets a hard constraint on valid input sourcing. It lacks an explicit exclusion for already-paired devices, which is the main missing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.