Skip to main content
Glama

adb_network_scan

Scan local networks for Android devices with ADB enabled over WiFi/TCP, probe common ADB ports and custom IP ranges, then connect discovered devices via adb_connect.

Instructions

Scan the local network for Android devices with ADB enabled over WiFi/TCP. Probes common ADB ports (5555-5558) on hosts from the ARP table and optionally a custom IP range. Discovered devices can be connected with 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_network_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
portsNoCustom ports to probe (default: [5555, 5554, 5556, 5557, 5558], max 20)
deviceNoDevice serial (used to determine the local subnet if no ipRange given)
ipRangeNoIP range to scan (e.g., '192.168.1.1-254'). If omitted, scans hosts from the ARP table only.
timeoutMsNoConnection timeout per host in ms (500-10000, default 2000)

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

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It discloses the probing mechanism and that an ARP-table-only scan happens when no range is given, which is useful, but it says nothing about expected scan duration, network-side effects, whether the scan is passive/safe for production devices, or the shape of the result beyond 'discovered devices'.

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 sentences, front-loaded with purpose, followed by mechanism and the natural next step. No filler and no restatement of the tool name.

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?

For a scan tool with no output schema and no annotations, an agent still lacks the return shape (list of host/port pairs?), an indication of how long a scan may take, and any caution about scanning subnets. What is present is accurate but not sufficient for confident invocation.

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 description coverage is 100%, so every parameter is already documented. The description adds marginal context by restating the default port set and the ARP-table fallback for ipRange, but says nothing about the device parameter's subnet-derivation role beyond what is already in the schema. Baseline 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 concrete verb and target: scan the local network for Android devices with ADB enabled over WiFi/TCP, and explains the mechanism (probe ports 5555-5558 on ARP-table hosts). It does not explicitly contrast with neighbors like adb_devices or adb_network_device_ip, but the scope is unambiguous.

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

Usage Guidelines3/5

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

The description implies usage by naming adb_connect as the follow-up action for discovered devices, which helps an agent chain calls. However, it never says when this tool should be preferred over adb_devices (already-connected devices) or adb_network_device_ip, and offers no exclusions or prerequisites.

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