Skip to main content
Glama

adb_network_connections

Show active TCP/UDP network connections on an Android device, including listening ports and connection states, to diagnose network activity.

Instructions

Show active network connections on the device (TCP/UDP). Similar to netstat — shows established connections, listening ports, and connection states.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
protocolNoFilter by protocolall

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

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose the shape of the output (established connections, listening ports, connection states), which is genuinely useful, but it omits whether the call requires root/privileged access, whether it is strictly read-only, and whether it can block or time out.

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, zero filler, and the core purpose is front-loaded before the netstat analogy. Nothing can 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?

For a two-parameter read tool with no output schema, the description covers intent and rough result content adequately. It is still thin on prerequisites (root access), result format, and how device selection defaults when the optional parameter is omitted.

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 'device' and the tcp/udp/all enum are already fully documented in the schema. The description's '(TCP/UDP)' phrasing only loosely gestures at the protocol filter, adding no meaning the schema lacks — 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 specific verb and resource ('Show active network connections on the device') and scopes it to TCP/UDP, so an agent knows this is a socket/port inspection tool. It does not name the nearby siblings (adb_network, adb_network_scan, adb_tcpdump_start) that an agent must choose between, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no named alternative. The netstat analogy implies a diagnostic context but leaves the agent to infer that adb_network_scan or adb_tcpdump_start are the right pick for other networking questions.

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