Skip to main content
Glama
Sign In
adb-ai

adb-ai

by cyberpunk2183
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

adb_close_app

Force-stop a running Android app on a chosen or default device to close it and free resources.

Instructions

Force-stop 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": {
      "app": "<app>"
    },
    "name": "adb_close_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYes
deviceNoserial, ip[:port] or saved alias; omit to use the default device

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. 'Force-stop' implies abrupt termination with likely unsaved-state loss, but the description never says what gets destroyed, whether system apps are permitted, what error occurs for a non-running or unknown package, or what is returned.

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?

Four words are certainly front-loaded and waste-free, but the brevity crosses into under-specification for a tool with an undocumented required parameter. Short is good here; too short is the problem.

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?

With no annotations, no output schema, and half the parameters undocumented, the description should at minimum explain the 'app' identifier format and the destructive consequences of force-stopping. Neither is present, so an agent cannot call it correctly without guessing or opening the schema.

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 description coverage is only 50%: the required 'app' parameter has no schema description and the description adds nothing about whether it expects a package name, an app label, or a component. Only 'device' is documented, and that documentation lives in the schema, not the description.

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 ('an app'), which cleanly separates it from the sibling adb_open_app. However, it never explicitly names the alternative or notes that it differs from a normal close, leaving the differentiation implicit.

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 guidance on when to use this versus adb_open_app, adb_shell, or other siblings, and no prerequisites (e.g., device must be connected, app must be running). The agent must infer usage entirely from the four-word phrase.

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