Skip to main content
Glama

adb_network_auto_connect

Scans a local network range for ADB devices and automatically connects to each responsive host on the chosen port, combining discovery and connection in one step.

Instructions

Discover and automatically connect to ADB devices on the local network. Combines network scanning with adb connect in one step. Probes a single port (default 5555) on each candidate; if you need to cover the full ADB port range (5555-5558) use adb_network_scan first, then adb_connect with the discovered host:port.

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

Input Schema

NameRequiredDescriptionDefault
portNoADB port to probe and connect (1-65535, default 5555)
deviceNoDevice serial (used to determine local subnet for ARP-based discovery)
ipRangeNoIP range to scan (e.g., '192.168.1.1-254')

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. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the key non-obvious behavior that probing is limited to one port per candidate and that connecting is performed as part of the call (an external state change). It does not say what happens on failed connects, whether existing connections are affected, whether it blocks/times out on a large ipRange, or what the result contains.

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 sentences, front-loaded with the primary action, then the behavioral constraint, then the routing alternative. No redundant restatement of the name or title, and every clause carries information the agent needs to choose or call the tool.

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 3-parameter, no-output-schema discovery tool with full schema coverage, the description covers purpose, port-probing scope, and sibling routing well. The remaining gap is that with an unannotated mutating side effect (creating a connection), it says nothing about failure behavior or what is reported back on success.

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%, so all three parameters are already documented in the schema, including the port default and range and the device param's ARP/subnet role. The description reinforces only the port default (5555) and the single-port constraint; it adds no extra syntax guidance for ipRange beyond the schema example.

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 compound verb+resource: discover ADB devices on the local network and connect to them in one step. It explicitly distinguishes itself from the closely-named siblings adb_network_scan (scan only) and adb_connect (connect to a known host:port) by defining its combined role.

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 alternative path with a concrete condition: 'if you need to cover the full ADB port range (5555-5558) use adb_network_scan first, then adb_connect'. Combined with the stated single-port default, an agent can decide between this tool and the two-step approach without guessing.

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