Skip to main content
Glama

adb_qemu_setup

Check and install QEMU for on-device virtualization by verifying KVM support and reporting version, with optional installation via the Termux package manager.

Instructions

Check and install QEMU for on-device virtualization. Verifies KVM availability, checks if QEMU is installed, reports version info, and can install QEMU via Termux package manager. Only available in on-device mode.

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_qemu_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
installNoIf true, install QEMU via pkg if not already present

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 must carry the behavioral load: it discloses the KVM verification step, the installed-check, version reporting, and that installation goes through the Termux package manager (implying a network fetch and system mutation). It does not state what happens on failure, whether install is idempotent, or what it returns on success, so the disclosure is partial.

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 front-loaded sentences that lead with the action and close with the availability constraint. Efficient, with no filler, though the enumerated sub-steps read slightly like a list rather than prioritized guidance.

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 one-parameter setup tool with no output schema, the description covers what is checked, what is optionally changed, and the environment restriction. The main residual gap is the shape of the result an agent should expect, which matters since the description claims it 'reports version info'.

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?

Only one parameter and its schema description already covers it at 100% ('If true, install QEMU via pkg if not already present'). The description's mention of installing via the Termux package manager restates rather than extends that, so baseline 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+resource pair ('Check and install QEMU') and enumerates the sub-actions (KVM check, install check, version report, install). It is distinct from adb_qemu_start or adb_qemu_status, though it never names those siblings to sharpen the boundary.

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 'Only available in on-device mode' line is a genuine applicability constraint, and the setup framing implies this runs before adb_qemu_start. But there is no explicit when-to-use/when-not statement or reference to the sibling qemu tools it precedes.

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