Skip to main content
Glama
Sign In
adb-ai

adb-ai

by cyberpunk2183
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

adb_pair_qr_finish

Wait for an Android device to scan the QR code, complete pairing, and establish the ADB connection, blocking until success or the specified timeout expires.

Instructions

Wait for the device to scan the code from adb_pair_qr_start, pair with it, and connect. Blocks until it happens or the timeout runs out.

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

Input Schema

NameRequiredDescriptionDefault
timeout_secondsNohow long to wait, default 60

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the long-blocking, synchronous nature and the timeout bound, which are the critical traits for an agent deciding whether to call it. It omits failure/return behavior on timeout expiry, which is a moderate gap.

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 tight sentence that front-loads the action and ends with the timeout constraint. No redundant or filler content.

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 one-parameter, no-output-schema tool with no annotations, the blocking behavior, pairing target, and timeout are all covered. What is missing is only the failure-mode outcome when the timeout expires.

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 the single timeout_seconds parameter already documents 'how long to wait, default 60'. The description's mention of timeout reinforces but adds no new semantics beyond the schema, so the baseline 3 applies.

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?

Specific verb sequence (wait, pair, connect) tied to a distinct resource, and it explicitly names the sibling adb_pair_qr_start whose output it consumes. An agent can distinguish it from adb_connect or adb_pair_qr_start without opening the schema.

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?

The dependency on adb_pair_qr_start makes the correct call ordering clear, and 'blocks until it happens or the timeout runs out' implies it should only be invoked after the code is displayed. It stops short of stating exclusions or what to do if pairing fails.

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