Skip to main content
Glama

adb_forward_list

Lists all active port forwards and reverse forwards for Android devices, optionally filtered by device serial, to help inspect current ADB forwarding rules.

Instructions

List all active port forwards and reverse forwards

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

Input Schema

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

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries full behavioral burden; it implies a read-only enumeration via 'List ... active', which is useful. However it says nothing about whether the device must be online, whether it errors when no forwards exist, or what the entries contain, leaving meaningful gaps for an unannotated tool.

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?

One short sentence, front-loaded with the verb and covering both forward directions without wasted words. It is perhaps slightly too terse given the absence of annotations, but nothing is redundant.

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 optional parameter, no output schema, no annotations), and the description covers the core action. It still omits the return shape and error behavior, which the absent output schema and annotations would otherwise have to supply.

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?

The single 'device' parameter already has a schema description ('Device serial (omit for all devices)') at 100% coverage, so the baseline is 3. The description adds no interpretation of the parameter, such as whether reverse forwards from other devices are included or how results are grouped per device.

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 ('List') and resource ('port forwards and reverse forwards') with scope qualifier 'all active'. An agent can distinguish it from adb_forward/adb_reverse, which create forwards, though it never names those siblings explicitly.

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?

The description gives no when-to-use guidance, no mention of prerequisites (device must be connected), and no routing away from similar siblings such as adb_tunnel_list or adb_devices. Usage is only implied by the fact that it is a listing operation.

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