Skip to main content
Glama

phone_stop_app

Force-stops an Android app by package name when the phone is connected via USB; unsaved work in that app is lost.

Instructions

Force-stop an app by package (needs the phone on USB). Unsaved work in that app is lost.

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": {
      "package": "<package>"
    },
    "name": "phone_stop_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With zero annotations the description carries the full burden, and it does disclose the most important trait: the operation is destructive in that unsaved work in the target app is lost. It omits other behavior an agent would want, such as error behavior for an invalid or non-running package and what the call returns on success.

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?

Two short sentences with the action and the key side effect front-loaded; nothing is padded. The parenthetical prerequisite is slightly awkward in placement but costs almost no reading effort.

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 single-parameter mutation tool with no annotations and no output schema, the definition covers the essential risk (data loss) and a hard prerequisite (USB connection). The remaining gaps, package value format and return/error behavior, are minor but real.

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 description coverage is 0%, so the description must compensate. "By package" clarifies that the single parameter is an app package identifier rather than an app name, but it gives no format example or pointer to a sibling such as phone_apps for discovering valid values.

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?

"Force-stop an app by package" gives a specific verb (force-stop) and resource (an app identified by package), which is clearly distinct from the open/launch behavior implied by siblings like phone_open_app. It stops short of naming a sibling or spelling out scope, but the action 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 Guidelines3/5

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

The parenthetical "needs the phone on USB" is a useful prerequisite that tells the agent when the call can succeed. However, there is no guidance on when to choose force-stop over alternatives (e.g., phone_open_app to relaunch, phone_apps to find the package), so usage is only implied.

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