Skip to main content
Glama

adb_tcpip

Switch a USB-connected Android device to TCP/IP mode on a chosen port so you can disconnect USB and connect over the network via ADB.

Instructions

Switch a USB-connected device to TCP/IP mode on the specified port (default 5555). After this, you can disconnect USB and use adb_connect.

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

Input Schema

NameRequiredDescriptionDefault
portNoTCP port for ADB (1-65535, default 5555)
deviceNoDevice serial (must be USB-connected)

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. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  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 full behavioral burden. It does disclose the meaningful side effect (the device switches transport mode) and the immediate consequence (USB can be unplugged), but it omits whether the change persists across reboots, how to revert to USB, and whether the ADB daemon restarts or the connection drops mid-call.

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 short sentences with zero filler: the operation and its default are front-loaded, then the workflow consequence. Nothing is repeated unnecessarily and every clause earns its place.

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 two-optional-parameter tool with no output schema, the description covers the prerequisite, the default port, and the next step, which is enough to call it correctly. The small gap is the absence of any note on reversibility or recovery if the port is unreachable after the switch.

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%, so both 'port' (range and default) and 'device' are already documented in structured form; the description only restates the default port and the USB-connected constraint. Baseline 3 is appropriate since the schema does the heavy lifting and the description adds no new parameter meaning.

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?

States a specific verb and resource ('Switch a USB-connected device to TCP/IP mode') plus the scope of the operation (specified port, default 5555). It also positions itself relative to the adb_connect sibling by naming it as the follow-up step, so an agent can tell the two apart without inspecting either schema.

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?

Gives a clear precondition ('USB-connected device') and a clear sequencing instruction ('After this, you can disconnect USB and use adb_connect'), which effectively tells the agent when this tool belongs in a workflow. It stops short of explicit exclusions, such as what to do for a device already on TCP/IP or which sibling to use to revert.

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