Skip to main content
Glama

adb_disconnect

Terminate a wireless ADB connection to an Android device using its IP:port, or omit the host to terminate all wireless device connections.

Instructions

Disconnect from a wireless device, or all wireless devices if no host specified

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

Input Schema

NameRequiredDescriptionDefault
hostNoDevice IP:port to disconnect (omit for all)

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. Changed2 schema fields changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / host / pattern
      Added value: +"^(?:\\d{1,3}\\.\\d{1,3}\\.\\d{1,3}\\.\\d{1,3}|\\[[0-9a-fA-F:]+\\]|[a-zA-Z0-9][a-zA-Z0-9.-]*):\\d{1,5}$"
  3. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the most important trait — that with no host argument the operation fans out to ALL wireless devices — but it says nothing about prerequisites (wireless debugging enabled), failure behavior when no device is connected, or whether the operation is idempotent.

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 sentence with zero waste; the scope-of-effect clause is attached directly to the action so the agent reads the conditional behavior up front.

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 one-optional-parameter, no-output-schema tool, the definition covers the essentials: action, target format via schema, and the all-devices fallback. The remaining gap is lack of sibling disambiguation (notably adb_qemu_disconnect) and any error/permission expectations.

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%, and the schema's own text ('Device IP:port to disconnect (omit for all)') already conveys the omit-for-all semantics. The description restates that fact rather than adding format detail, so the baseline 3 applies.

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+resource ('Disconnect from a wireless device') plus the scope of effect when the target is omitted. An agent knows exactly what the tool does, though it does not distinguish itself from the similarly-named sibling adb_qemu_disconnect, which also disconnects but for QEMU guests.

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?

The clause 'or all wireless devices if no host specified' implicitly tells the agent that omitting the parameter is a valid, deliberately broad mode, which is useful. However, there is no explicit routing guidance: nothing points to adb_connect for the inverse operation, to adb_devices for discovering connected hosts, or explains how this differs from adb_qemu_disconnect.

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