Skip to main content
Glama

adb_qemu_start

Boot a KVM-accelerated QEMU virtual machine with automatic CPU and RAM sizing, optional safe custom limits, and ADB port forwarding for guest access.

Instructions

Boot a QEMU virtual machine with KVM hardware acceleration. Auto-detects optimal resource allocation: uses total cores minus 1 for the VM (reserving one for the host OS), and up to 65% of physical RAM. Custom values are accepted but capped at safe limits to prevent host starvation.

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": {
      "name": "<name>",
      "image": "<image>"
    },
    "name": "adb_qemu_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpusNoVirtual CPUs. Auto-detected if omitted (total cores minus 1). Capped at safe limit.
nameYesVM name (used to track and stop the VM)
imageYesDisk image filename (from adb_qemu_images) or absolute path
appendNoKernel command line arguments (for Android boot).
initrdNoPath to initrd/ramdisk image (for Android boot).
kernelNoPath to kernel image (for Android boot). If omitted, QEMU uses the disk image's bootloader.
adbPortNoHost port to forward to guest ADB (port 5555). Default 5556.
displayNoDisplay output. 'none' for headless (default). 'vnc' starts a VNC server on port 5900.none
memoryMbNoRAM in MB. Auto-detected if omitted (65% of physical RAM). Capped at safe limit.

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

A3.5/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 does disclose KVM acceleration, automatic CPU/RAM allocation, and safe caps to prevent host starvation. It does not cover lifecycle details such as name conflicts, background execution, ADB port side effects, or failure behavior, so important operational context is missing.

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 tight sentences front-load the purpose and then explain resource defaults with no filler. The second sentence is dense but earns its length by clarifying safety behavior.

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?

The description covers the main action and resource policy for a nine-parameter VM-start tool, but with no annotations or output schema it omits lifecycle, return/connection expectations, and prerequisite flow (image selection, setup). The schema supplies parameter detail, but the description is not fully complete for the 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 coverage is 100%, so all nine parameters are documented in the schema; the description mainly reinforces auto-detection and capping for cpus/memoryMb rather than adding new meaning. Baseline 3 is appropriate.

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?

The description states a specific action ('Boot') and resource ('QEMU virtual machine') and adds KVM hardware acceleration, so it is distinguishable from stop/status/connect siblings. It does not explicitly name sibling tools or when to prefer this over emulator start, but the core purpose is clear.

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?

It implies the tool is for starting a QEMU VM, but gives no explicit when-to-use, prerequisites, or alternatives such as adb_emulator_start or adb_qemu_connect. That leaves routing to inference.

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