Skip to main content
Glama

adb_reverse_remove

Remove a specific reverse forward (device to host) or all reverse forwards to clean up ADB mappings after testing.

Instructions

Remove a reverse forward (device → host), or all reverse 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_reverse_remove"
  }
}

Input Schema

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

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 / remote / description
      Previous value: -"Remote spec to remove (e.g., 'tcp:3000'). Omit to remove all reverse forwards."New value: +"Remote spec to remove (e.g., 'tcp:3000'). Omit to remove all reverse forwards. AF2 fix: format-validated."
    • addedInput schema / properties / remote / 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

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose the key destructive mode: omitting the remote spec wipes all reverse forwards. It says nothing about idempotency (what happens when the spec is not present), whether errors are raised, or whether the operation affects other devices.

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?

Two short sentences, front-loaded with the action and scoped immediately by direction. No filler wording; nothing to trim.

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?

For a two-optional-parameter tool with no output schema and no annotations, the description covers what it does and one clean-up scenario. It is adequate but leaves gaps around idempotency and failure behavior that an agent would want before calling it in cleanup flows.

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 a format pattern and an example, so the schema already explains both parameters fully. The description's 'or all reverse forwards' restates the omit semantics that the schema already documents, adding little beyond the baseline.

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?

The description gives a specific verb and resource, 'Remove a reverse forward', and clarifies the direction as device → host, which separates it cleanly from adb_forward_remove. It stops short of naming the sibling outright, but the direction semantics do the differentiating work.

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?

'Use after testing to clean up' gives a lightweight usage context, and the description notes the omit-to-remove-all mode. There is no mention of the creating counterpart (adb_reverse), no prerequisites, and no guidance on when to remove a single spec versus everything.

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