Skip to main content
Glama

adb_emulator_start

Launch an Android Virtual Device emulator by name and return once the emulator process starts, with options for GPU mode, cold boot, and headless operation.

Instructions

Launch an Android Virtual Device (AVD) emulator. Returns once the emulator process has started.

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": {
      "avdName": "<avdName>"
    },
    "name": "adb_emulator_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
avdNameYesAVD name (from adb_avd_list)
gpuModeNoGPU acceleration modeauto
coldBootNoForce cold boot (-no-snapshot-load)
headlessNoRun without GUI window (-no-window)

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.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important behavior: it returns as soon as the process starts, not when the device is booted, which warns the agent that follow-up readiness checks are needed. It says nothing about resource consumption, whether the emulator persists in the background, what happens if an AVD is already running, or failure conditions.

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 short sentences, purpose first, with the practically important return-timing caveat second. No filler or restated title text.

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 process-launching tool with no annotations and no output schema, the definition covers what it does and when it returns, but omits prerequisites (emulator SDK availability), pre-conditions (AVD already running), and the expected follow-up of waiting for boot. Adequate but with clear gaps for a state-changing launch operation.

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 every parameter including the gpuMode enum and the coldBoot/headless flags is already documented in the schema with their underlying emulator flags. The description adds no additional parameter meaning, so the baseline of 3 applies.

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: "Launch an Android Virtual Device (AVD) emulator." This clearly separates it from adb_emulator_stop and adb_avd_list, though it does not explicitly distinguish it from the nearby adb_qemu_start / adb_ci_wait_boot siblings.

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 when-to-use or when-not-to-use guidance. The description never says to call this before wait/boot-check tools or that a running emulator should be stopped first, leaving the agent to infer sequencing from sibling names alone.

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