Skip to main content
Glama

Stop Adb App

stop_adb_app
Destructive

Force-stop all processes of an Android package via adb to end a dynamic-analysis run. Specify the device serial and package to terminate its running processes.

Instructions

Force-stop every process of one package (am force-stop), ending a dynamic-analysis run. A device-mutating tool; it succeeds whether or not the package had running processes.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serial": "emulator-5554",
      "package": "com.example.app"
    },
    "name": "stop_adb_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYesDevice serial exactly as `adb devices` reports it
packageYesPackage whose processes are force-stopped

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructive, openWorld, and non-idempotent, so the safety profile is covered; the description adds real value by naming the underlying `am force-stop` semantics and stating the success condition holds even with no running processes. It does not clarify permission requirements or what happens to persisted state, but the added context is substantive.

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 tight sentences: the operation and its effect come first, then the behavioral caveat. No filler, and the most important constraint is front-loaded.

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-parameter mutation tool with no output schema and safety already covered by annotations, the description supplies scope (one package on one device), effect (all processes killed), and success semantics. Only permission prerequisites and interaction with an ongoing run's artifacts are unaddressed.

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%, with both `serial` and `package` fully documented including patterns and an example, so the schema carries the weight. The description only restates scope ('one package') and adds no format or edge-case detail beyond that, which is the expected baseline.

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 ('Force-stop every process of one package') and grounds it in the underlying command (`am force-stop`). The phrase 'ending a dynamic-analysis run' distinguishes it from siblings like start_adb_app without needing the schema opened.

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?

Implies the usage context by tying it to ending a dynamic-analysis run, which is useful lifecycle framing. However, it gives no explicit when-not guidance or pointer to alternatives (e.g., uninstall_adb_package vs. merely stopping), leaving the agent to infer boundaries.

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