rn-device-mcp

Overview Schema Source Related Servers Discussions Admin

Force-stop an app

android_stop_app

Force-stops an Android app by package name to terminate it during testing or troubleshooting, with optional device serial targeting.

Instructions

Force-stops the app.

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": "android_stop_app"
  }
}

Input Schema

Name	Required	Description	Default
`serial`	No	adb serial (from android_devices). Default: the only online device.
`packageName`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

C2.1/5.0

Behavior2/5

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

Annotations already mark this as a non-read-only, non-destructive operation, and the description adds nothing beyond them — no mention that unsaved state is lost, that running services/background processes are killed, or whether a not-running package causes an error. This mild tension with destructiveHint=false is left unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no wasted words, but its brevity reflects under-specification rather than disciplined conciseness. It is not poorly structured, just nearly content-free.

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

Completeness2/5

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

For a mutation tool with no output schema and one undocumented required parameter, the definition should explain side effects, failure modes, and return behavior. None of that is present, leaving the agent to guess at consequences of force-stopping.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: the serial parameter is documented in the schema, but packageName has only a type and minLength. The description does nothing to clarify the expected package identifier format (e.g., com.example.app) or its required nature, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Force-stops the app.' restates the name and title without adding specificity; it never says what 'force-stop' means at the OS level or how it differs from the sibling ios_terminate_app / android_launch_app. Only the verb+resource is conveyed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool rather than launching, terminating, or restarting an app, and no stated prerequisites (e.g., device must be online, app must be installed/running). The agent must infer usage entirely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.