Skip to main content
Glama

adb_emulator_stop

Stop a running Android emulator gracefully via ADB by specifying its device serial or AVD name; omit both to list running emulators.

Instructions

Stop a running emulator. Uses 'adb emu kill' for graceful shutdown.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adb_emulator_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoEmulator device serial (e.g., 'emulator-5554') — alternative to avdName
avdNameNoAVD name to stop. If omitted, lists running emulators.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

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 full behavioral burden; it does disclose the underlying mechanism ('adb emu kill') and that the shutdown is graceful, which is real added context. It is silent on what happens to AVD state/snapshots, whether in-flight work is interrupted, and failure behavior when no emulator matches.

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, front-loaded with the action and followed by the implementation detail. No wasted wording, though the second sentence could have been spent on differentiation instead of mechanism alone.

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 zero-required-parameter, fully documented tool with no output schema, this is nearly complete; the agent knows what it does and how. The missing piece is disambiguation from other stop/restart siblings in a very large tool set.

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 both optional parameters (device, avdName) and their alternatives are already documented in the schema. The description adds no additional meaning about how the parameters interact or what happens when both are given.

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 and resource: 'Stop a running emulator,' which tells an agent exactly what the tool does. It does not distinguish itself from nearby siblings such as adb_qemu_stop or adb_reboot, so the agent must infer which stop mechanism applies.

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 explicit guidance on when to use this instead of adb_qemu_stop, adb_reboot, or adb_force_stop, nor on preconditions (emulator must be running, one vs. multiple emulators). The only routing hint — that omitting avdName lists running emulators — lives in the schema, not the description.

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