Skip to main content
Glama

adb_forward_remove

Remove a specific host-to-device port forward or clear all forwards after testing to clean up ADB connections.

Instructions

Remove a port forward (host → device), or all forwards. Use after testing to clean up.

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

Input Schema

NameRequiredDescriptionDefault
localNoLocal spec to remove (e.g., 'tcp:8080'). Omit to remove all forwards. AF2 fix: format-validated.
deviceNoDevice serial

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. Changed3 schema fields changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / local / description
      Previous value: -"Local spec to remove (e.g., 'tcp:8080'). Omit to remove all forwards."New value: +"Local spec to remove (e.g., 'tcp:8080'). Omit to remove all forwards. AF2 fix: format-validated."
    • addedInput schema / properties / local / pattern
      Added value: +"^(tcp:\\d{1,5}|localabstract:[A-Za-z0-9_./-]+|localreserved:[A-Za-z0-9_./-]+|localfilesystem:[A-Za-z0-9_./-]+|dev:[A-Za-z0-9_./-]+|jdwp:\\d+)$"
  3. First observedv1.1.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does disclose destructive removal plus the potentially broad 'all forwards' scope. It provides little further operational context, such as no-match handling, error behavior, or how device selection limits the removal.

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 compact clauses front-load the operation and scope, then give a practical cleanup use case. There is no redundant or unnecessary wording.

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

Completeness4/5

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

For a simple two-parameter operation with a fully described schema, the direction, scope, and cleanup context are nearly sufficient for correct invocation. Missing no-match/error behavior and clarification of optional device targeting prevent full completeness, particularly without annotations or an output schema.

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%, including the local-spec formats and the fact that omitting local removes all forwards. The description reinforces the scope but adds no parameter syntax, targeting, or validation details beyond the schema.

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—removing ADB port forwards—and states both the direction (host → device) and the single-versus-all scope. The direction helps distinguish it from reverse-forward removal, while 'remove' separates it from creating or listing forwards.

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

Usage Guidelines4/5

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

The phrase 'Use after testing to clean up' supplies a concrete invocation context. It does not explain when removing all forwards is inappropriate or route related cases to siblings such as adb_forward_list or adb_reverse_remove.

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