Skip to main content
Glama
Sign In
adb-mcp

adb-mcp

by FlashZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_forwards

List active adb forward rules for an Android device, optionally filtered by serial. Returns local and remote port mappings.

Instructions

List active adb forward rules: [{serial, local, remote}].

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": "list_forwards"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. The qualifier 'active' hints that inactive/dead rules are excluded, but the description does not state safety profile, permissions, or operational side effects for a tool in a device-mutating adb suite.

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?

A single front-loaded sentence with zero filler; the scope ('active') and return preview are packed efficiently. Nothing needs trimming.

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?

An output schema exists, so return values need no explanation. However, the lone `serial` parameter is undocumented in both schema and description, and there is no routing guidance among the many forward/reverse siblings, leaving real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one optional parameter (serial) with 0% schema description coverage, and the description never explains what it does (device scoping/filtering). The `{serial, local, remote}` snippet describes the output shape, not the parameter, so it fails to compensate for the schema gap.

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 (active `adb forward` rules) and even previews the return shape. It is distinguishable from siblings like list_reverses, forward_port, remove_forward, and clear_forwards, though it never names them.

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?

Usage is only implied by the verb 'List' and the word 'active'. There is no explicit when-to-use, no condition selecting it over forward_port/list_reverses/remove_forward, and no note that it is a read-only inspection step.

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