Skip to main content
Glama
Sign In
adb-ai

adb-ai

by cyberpunk2183
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

adb_pair_qr_start

Generates a QR code to start pairing a new Android 11+ phone or tablet with this machine over wireless debugging; scan it on the device, then finish pairing.

Instructions

Begin pairing an Android 11+ phone or tablet by QR code. Returns a QR image to show the person; they point the device's camera at it from Wireless debugging > 'Pair device with QR code'. Then call adb_pair_qr_finish. Use this when a device has never been paired with this machine; an already-paired device just needs adb_connect.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations, so the description carries the full burden; it discloses the key behavior that the call returns a QR image for the person to scan and that pairing is incomplete until adb_pair_qr_finish. It omits failure modes such as QR expiry, timeout, or same-network requirements, which would matter for this handshake flow.

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 front-loaded sentences: what it does, what comes back and how the human consumes it, then when to use it versus the connect sibling. No filler or restatement of the 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?

With no output schema and no annotations, the description does the work of explaining the returned QR image and the required follow-up call. It is nearly sufficient, lacking only session lifetime/expiry details an agent might need when the human takes too long to scan.

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?

Zero parameters, so there is nothing for the description to clarify and the baseline of 4 applies. No misleading parameter claims are present.

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 and resource ('Begin pairing an Android 11+ phone or tablet by QR code') with an explicit platform/version scope, and names the follow-up sibling adb_pair_qr_finish plus the alternative adb_connect. An agent can distinguish it from every sibling without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit selection rule: use this when a device has never been paired with this machine, otherwise an already-paired device just needs adb_connect. It also prescribes the two-step sequence and the human UI path for invoking it.

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