Skip to main content
Glama

adb_tcpdump_stop

Stop an active Android packet capture and pull the pcap file locally for analysis, so you can end capture and inspect network traffic.

Instructions

Stop an active packet capture and pull the pcap file locally for analysis.

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

Input Schema

NameRequiredDescriptionDefault
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. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.5/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 burden. It does disclose two behaviors beyond the name: terminating the capture and transferring the pcap to the local host — useful for a mutation tool. However, it omits where the file is written, whether the remote capture is cleaned up, and what happens if no capture is active.

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 front-loaded sentence that names the action, its object, and the side effect with zero filler. 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.

Completeness3/5

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

The tool is simple (one optional param, no nesting), but with no annotations and no output schema, the description should state the destination/format of the pulled pcap and the failure mode when no capture is running. As written, an agent knows what it does but not what it gets back or where it lands.

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 coverage is 100% for the single 'device' parameter, so the schema already defines it as a device serial. The description adds nothing about whether device is required or how it resolves to a target, so 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 ('Stop') and resource ('active packet capture') plus a second concrete effect ('pull the pcap file locally'). An agent can distinguish it from adb_tcpdump_start without inspecting the schema, though the description never names the sibling pair explicitly.

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?

Usage is only implied by the phrase 'an active packet capture' — the agent must infer that a prior adb_tcpdump_start is a prerequisite and that calling it with no capture running is invalid. No explicit when-not guidance or alternative tools are named.

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