Skip to main content
Glama

adb_tunnel_list

Lists active managed ADB tunnels created via adb_tunnel_open, showing tunnel ID, device, direction, and both endpoints so you can inspect or filter tunnels by device.

Instructions

List all active managed tunnels (opened via adb_tunnel_open). Shows tunnel ID, device, direction, and both endpoints. Note: this only surfaces tunnels created via adb_tunnel_open — tunnels created via the low-level adb_forward / adb_reverse won't appear here. For those, use adb_forward_list.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoFilter to a specific device serial (default: all devices)

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. Addedv1.1.3

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the disclosure burden and does well: it enumerates the returned fields (tunnel ID, device, direction, both endpoints) and warns that low-level forwards are invisible in the result, which prevents a false-negative conclusion. It stops short of stating whether a device must be connected or what an empty result means.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and its scope, followed by return fields, then the caveat. The 'only surfaces ... won't appear here' phrasing restates the same exclusion twice, which is slightly redundant but harmless given the risk of a wrong conclusion.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter list tool with no output schema and no annotations, the description covers action, scope, returned fields, and the key failure mode (missing low-level tunnels). An agent has everything needed to call it and interpret the result 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 description coverage is 100% and the single 'device' filter is fully documented there as 'Filter to a specific device serial (default: all devices)'. The description never mentions the filter, so it adds no meaning beyond the schema; 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?

The description gives a specific verb and resource ('List all active managed tunnels') and immediately scopes it to tunnels opened via adb_tunnel_open. It also names precisely which sibling covers the other case (adb_forward_list), so an agent can distinguish it from the lookalike adb_forward_list without opening either schema.

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?

It states both when to use this tool (managed tunnels from adb_tunnel_open) and when not to (tunnels created via the low-level adb_forward / adb_reverse), explicitly routing to adb_forward_list as the alternative. Nothing about tool selection is left to inference.

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