Skip to main content
Glama
Sign In
mobilerun-mcp

mobilerun-mcp

by impeterwayne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Stop App

stop_app

Force-stop an app on a device, optionally wiping its data to reset state before relaunching or troubleshooting.

Instructions

Force-stop an app; clear_data also wipes its data.

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": {
      "app_id": "<app_id>"
    },
    "name": "stop_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYes
deviceNo
clear_dataNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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. It usefully discloses the destructive side effect that 'clear_data also wipes its data', which is the key risk an agent must know. However, it omits that a force-stop kills the running process and loses unsaved state, permission requirements, and any failure modes.

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

Conciseness4/5

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

A single compact sentence with the primary action front-loaded and the destructive caveat appended. No wasted words, though the extreme brevity leaves behavioral gaps rather than padding them.

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?

An output schema exists, so return values need not be described. For a mutation tool with no annotations and undocumented parameters, the description covers the most important destructive consequence but leaves the device targeting and preconditions unexplained.

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 0% across three parameters, so the description must compensate. It explains the semantic effect of clear_data (wipes app data), which is more than the schema's bare boolean, but says nothing about app_id format or how the device parameter selects a target.

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?

The description states a specific verb and resource ('Force-stop an app'), which cleanly separates it from launch_app/start_app and other app-lifecycle siblings. It does not explicitly name alternatives, but the verb itself is unambiguous.

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 versus start_app, uninstall_app, or press_home, and no prerequisites (e.g., app must be running/installed). Usage is only implied by the tool name.

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