Skip to main content
Glama
Sign In
devilge

devilge

by Yercko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Force-stop an app

devilge_force_stop_app
Idempotent

Kill all processes of a specified Android app. Useful to ensure a cold start on relaunch or to stop a hung app.

Instructions

Runs am force-stop <pkg> — kills every process of the given app. Useful before relaunch to ensure a cold start, or when an app is hung.

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

Input Schema

NameRequiredDescriptionDefault
serialNoDevice serial. Defaults to DEVILGE_DEFAULT_DEVICE_SERIAL or the only attached device.
packageNameYesApp applicationId to kill.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A3.5/5.0
Behavior1/5

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

Description states 'kills every process', indicating destructive behavior, but annotations include destructiveHint=false, a clear contradiction. No further details on side effects or irreversibility.

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 concise sentences, front-loaded with the core command and purpose, no unnecessary words.

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?

While the core action is clear, the contradiction with annotations undermines completeness. No output schema exists, but the return value is implied. Additional context on process-killing effects would improve completeness.

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 100%, so the description adds no extra meaning beyond the schema. The description does not elaborate on parameter formats or constraints.

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?

The description clearly specifies the action ('force-stop'), the target resource ('app'), and the underlying command ('am force-stop'). It distinguishes from sibling tools like launch_app by stating it kills all processes.

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

Usage Guidelines4/5

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

Explicitly mentions two use cases: ensuring cold start before relaunch and handling hung apps. While it doesn't explicitly list when not to use, the positive scenarios provide sufficient guidance.

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