Skip to main content
Glama
Sign In
Karagöz

Karagöz

by yagizdo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Stop an app

terminate

Force-stop every process of a specified app package on a connected Android or iOS device to end app activity and release resources.

Instructions

Force-stop every process of an 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": {
      "package": "<package>"
    },
    "name": "terminate"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoId or name.
packageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations establish this is a non-read-only but non-destructive mutation, and 'Force-stop' adds the meaningful nuance that processes are killed rather than gracefully shut down (implying loss of unsaved state). Beyond that the description says nothing about idempotency, what happens if the app is not running, or whether other apps are affected. There is mild tension with destructiveHint=false, but force-stopping does not itself destroy persisted data, so this is not a contradiction.

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 front-loaded sentence with zero filler; nothing redundant is present. It is arguably too terse given the unexplained required parameter, but there is no structural waste.

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 two-parameter tool with no output schema the scope is small, but the description leaves the required 'package' argument undefined and gives no signal about the result of the operation (success confirmation, error when the app is absent). Adequate as a minimum, with clear gaps.

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 only 50%: 'device' is documented as 'Id or name', but 'package' has no schema description and the tool description never clarifies its expected format (bundle id, app id, or a display name). With a low-coverage schema, the description should compensate and does not.

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 verb ('force-stop') and resource ('every process of an app'), which is more informative than the generic title 'Stop an app'. It implicitly separates itself from 'uninstall' and 'launch', but never names a sibling to sharpen the boundary.

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?

No indication of when to choose terminate over uninstall, launch, or a restart flow, and no prerequisites (device connectivity, app installed, permissions). The agent must infer the usage context entirely.

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