Skip to main content
Glama

adb_qemu_connect

Connect to a running QEMU VM's ADB service to expose its guest as an ADB device for DeepADB tools; the guest must have an ADB daemon running.

Instructions

Connect to a running QEMU VM's ADB service, making the guest appear as a device for DeepADB tools. Requires the guest OS to have an ADB daemon running (e.g., Android guest with USB debugging enabled). Requires the 'adb' binary (install with: pkg install android-tools). Connections are restricted to localhost only — no remote host connections allowed.

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>"
    },
    "name": "adb_qemu_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesVM name to connect to (must be running)
timeoutNoConnection timeout in milliseconds (3s-30s). Default 10s.

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.6/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. It discloses the localhost-only restriction and the ADB-daemon prerequisite, which are genuinely useful behavioral facts, but says nothing about idempotency (what happens if this VM is already connected), error behavior on timeout, or how the connection is torn down.

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?

Leading sentence states purpose and effect, followed by prerequisites and a hard constraint; each sentence earns its place. The install hint is slightly incidental but practical, and nothing is padded.

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 connection-establishing tool with no output schema and no annotations, the description should say what a successful connect returns or how failures surface, and it does not. Prerequisites and the localhost restriction are covered, but the lifecycle around the connection is only half-told despite adb_qemu_disconnect existing as a sibling.

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 'name' and 'timeout' are fully documented in the schema, including the 3s-30s bounds and default. The description adds no extra meaning about parameter interpretation beyond repeating the 'must be running' condition.

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 ('Connect to a running QEMU VM's ADB service') plus the resulting effect (guest appears as a DeepADB device), which clearly separates it from adb_connect or adb_pair. It never explicitly names those siblings, so differentiation relies on the 'QEMU VM' qualifier rather than a direct contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Preconditions are spelled out concretely: ADB daemon running in the guest, USB debugging enabled, adb binary installed, and the VM must be running. What is absent is guidance on when to pick this over adb_connect or when to follow up with adb_qemu_disconnect, so the alternative-selection layer is left 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