Skip to main content
Glama

adb_restart_app

Force-stops and relaunches an Android app by package name, combining the common debugging restart workflow into a single ADB call.

Instructions

Force-stop then re-launch an app. The most frequent debugging workflow in a single call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "packageName": "<packageName>"
    },
    "name": "adb_restart_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
delayMsNoDelay between stop and start in ms (0-10000, default 500)
packageNameYesPackage name (e.g., 'com.example.app')

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

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the ordering of operations but omits that force-stopping kills the process and loses in-memory state, whether app data is preserved, and what the call returns or does on failure.

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 waste; the core action is front-loaded and the second sentence adds a usage signal rather than filler.

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?

For a simple three-parameter tool with a fully documented schema and no output schema, the description covers the core action adequately. However, with no annotations and no mention of state loss or failure modes, an agent lacks the behavioral context needed to use it safely.

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%, including the delayMs range and default and the packageName example, so the schema already does the heavy lifting. The description adds no additional meaning about parameters, making the baseline 3 appropriate.

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 compound action ("Force-stop then re-launch") on a specific resource (an app), which distinguishes it from adb_force_stop and adb_start_app by making the composition explicit. It only implies the composite nature rather than naming those siblings directly, so it falls short of 5.

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 most frequent debugging workflow in a single call" hints that this is the preferred shortcut over two separate calls, but it never states when to prefer adb_force_stop plus adb_start_app instead, nor any preconditions such as the package being installed or the device being connected.

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