Skip to main content
Glama
Sign In
android-emulator

android-emulator

by Sajinthan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

shutdown_emulator

Shut down a running Android emulator to free system resources and end active sessions. Specify the device serial when multiple emulators are connected.

Instructions

Shut down a running emulator

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

Input Schema

NameRequiredDescriptionDefault
serialNoDevice serial (e.g. emulator-5554). Optional when exactly one device is connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 full responsibility for behavioral disclosure. It only states the action without revealing side effects such as unsaved state loss, whether the shutdown is graceful, or what occurs if the emulator is not running. This is a significant gap for a potentially destructive operation.

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?

The description is a single sentence with no filler, leading with the action verb and resource. It is optimally concise and front-loaded.

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 tool with one optional parameter and no output schema, the description is minimal but might suffice. However, it could be more complete by mentioning the effect on running processes or the need for a booted emulator. The lack of any behavioral caveats leaves room for improvement.

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?

The input schema already fully describes the single 'serial' parameter, including its optionality and example. The description adds no parameter-level information, so the baseline of 3 applies given 100% schema coverage.

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 states the verb 'shut down' and the resource 'running emulator', making its purpose unambiguous. It is distinctly opposite to sibling tools like boot_emulator and does not require inference.

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 description implies when to use the tool (when an emulator is running and needs to be stopped) but provides no explicit guidance on alternatives or exclusion conditions. For example, it does not mention that boot_emulator is the tool for starting an emulator, leaving usage context implicit.

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