Skip to main content
Glama

adb_tcpdump_start

Starts a background tcpdump packet capture on an Android device, with optional interface and filter settings, to diagnose network traffic. Requires root or a tcpdump binary on the device.

Instructions

Start a packet capture on the device using tcpdump. Requires root or tcpdump binary on device. Capture runs in background.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
filterNotcpdump filter expression (e.g., 'port 443', 'host 10.0.0.1')
interfaceNoNetwork interface to capture (default: 'any')any
maxPacketsNoStop after N packets (1-1000000, omit for continuous until stop)

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

A3.7/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 burden and does add real value: it discloses the root/binary prerequisite and the background execution model. However, it omits critical behavioral facts an agent needs — where the captured packets are written, how to retrieve them, what happens if a capture is already running, or what error surfaces when root is absent.

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?

Three compact sentences with zero filler, front-loading the action, then the precondition, then the execution model. Nothing could be removed without losing information.

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

Completeness5/5

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

Given a simple four-parameter start tool with full schema coverage and no output schema, the description covers the action, the prerequisite, and the async nature. The missing stop-tool reference and output location are the only meaningful gaps.

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%, with filter syntax examples and the maxPackets range already documented in the schema. The description adds nothing about parameters, so the baseline 3 applies — the schema does all the work here.

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 — 'Start a packet capture on the device using tcpdump' — which an agent can instantly distinguish from sibling read-only tools like adb_network_connections. It does not, however, name the paired sibling adb_tcpdump_stop, so the lifecycle pairing is left implicit.

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 description gives a hard precondition ('Requires root or tcpdump binary on device') and notes the capture is asynchronous ('runs in background'), which is useful context for calling it. But it never says when to choose this over alternatives such as adb_network_connections or adb_network_scan, and never points to adb_tcpdump_stop as the way to end the capture.

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