Skip to main content
Glama

adb_connect

Connect to an Android device over WiFi/TCP by specifying its IP address and port; pair the device first or enable TCP/IP debugging before connecting.

Instructions

Connect to a device over WiFi/TCP. Device must be paired first or have TCP/IP enabled.

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>"
    },
    "name": "adb_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesDevice IP and port (e.g., '192.168.1.100:5555' or '192.168.1.100:41567')

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.7/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 adds the pairing/TCP/IP prerequisite, but says nothing about connection timeout, whether an existing connection is replaced, or whether the tool blocks until the device is reachable — all of which matter for a stateful connect 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?

Two short sentences with the action front-loaded and the prerequisite second. Nothing is redundant and nothing could be trimmed without losing information.

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?

The tool is simple (one required parameter, no nesting), and the description covers what it does and the precondition. With no output schema and no annotations, it leaves the return value and failure behavior undocumented, which an agent needs to chain this call correctly.

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 'host' parameter already documents the IP:port format with two concrete examples and a strict pattern. The description adds no syntax or format detail beyond that, 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 specific verb and transport ('Connect to a device over WiFi/TCP'), which is clearly distinct from siblings like adb_pair, adb_tcpip, adb_disconnect and adb_network_auto_connect. It does not name those siblings explicitly, so the agent must infer the boundary, but the resource and mode are unambiguous.

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?

'Device must be paired first or have TCP/IP enabled' gives a concrete precondition that implicitly routes the agent to adb_pair or adb_tcpip when unmet. It stops short of naming those alternatives or saying what to do when connection fails, so it is strong context rather than full when/when-not guidance.

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