Skip to main content
Glama

adb_qemu_guest_shell

Execute shell commands on a connected QEMU guest VM via ADB; derive the guest serial internally and apply the same security checks as standard ADB shell access.

Instructions

Execute a shell command on a QEMU guest VM via ADB. The VM must be connected first (use adb_qemu_connect). The guest serial is derived internally — no user-supplied host/IP reaches the ADB binary. Subject to the same security middleware checks as adb_shell.

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

Input Schema

NameRequiredDescriptionDefault
nameYesVM name (must be connected via adb_qemu_connect)
commandYesShell command to execute on the guest
timeoutNoCommand timeout in milliseconds (1s-60s). Default 15s.

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.8/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 add genuinely useful security context: the guest serial is derived internally, no user-supplied host/IP reaches the ADB binary, and the same middleware checks as adb_shell apply. It still does not disclose side effects of running arbitrary guest commands, output format, truncation, or failure behavior, which matters for a tool with no output schema.

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?

Three compact sentences, front-loaded with the action, then the precondition, then the security posture. No filler and nothing redundant with the schema.

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 three-parameter execution tool with complete schema coverage, the critical operational facts (connection prerequisite and the internal serial derivation) are covered. The main gap is the unstated return value, which matters more here because there is no output schema.

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% and each of the three parameters is documented, including the timeout bounds, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond repeating the connection precondition already stated in the 'name' field.

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: execute a shell command on a QEMU guest VM via ADB. The QEMU/guest qualifier differentiates it from the generic adb_shell sibling, though the contrast is only implied by the 'same security middleware checks as adb_shell' reference rather than stated outright.

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?

Explicitly names the prerequisite ('The VM must be connected first') and the tool that satisfies it (adb_qemu_connect), which is the main way an agent would misuse this. It stops short of saying when to prefer adb_shell or adb_root_shell over this tool.

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