Skip to main content
Glama
Sign In
adb-mcp

adb-mcp

by FlashZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_reverses

List active adb reverse port-forwarding rules for an Android device to inspect remote-to-local port mappings.

Instructions

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

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

Input Schema

NameRequiredDescriptionDefault
serialNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does not state that this is a read-only operation, what happens when serial is omitted (all devices?), or how active rules are defined, though it does hint at the return shape.

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 tight sentence with the resource front-loaded and a compact shape hint appended. Nothing is wasted.

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 the return-value shape need not be spelled out in prose. However, the description omits the meaning of the one parameter and the multi-device behavior, which are not covered anywhere else.

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?

Schema description coverage is 0% and the single `serial` parameter (nullable, default null) is never mentioned. The description does not explain whether serial scopes the query to one device or defaults to all, leaving a meaningful 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 and resource: 'List active `adb reverse` rules', which clearly identifies the reverse-port mapping inventory. It distinguishes itself from list_forwards/list_forwards by resource name, but does not explicitly contrast with those near-identical siblings.

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?

No guidance on when to use this versus list_forwards, remove_reverse, or clear_forwards, and no prerequisites or context. The agent must infer usage from the name alone.

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