Skip to main content
Glama

adb_qemu_stop

Stops a running QEMU virtual machine by sending SIGTERM for graceful shutdown, or SIGKILL when immediate forced termination is required.

Instructions

Stop a running QEMU virtual machine. Sends SIGTERM for graceful shutdown, with force kill option.

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

Input Schema

NameRequiredDescriptionDefault
nameNoVM name to stop. If omitted, lists running VMs.
forceNoUse SIGKILL instead of SIGTERM for immediate termination.

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 it does disclose the key signal semantics: SIGTERM for graceful shutdown versus SIGKILL when force is used. It does not say whether graceful stop preserves disk/snapshot state, what happens if the named VM is not running, or whether elevated permissions are needed — meaningful gaps for a destructive operation.

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 short sentences with the action front-loaded and the signal behavior second — no filler. The phrasing is slightly redundant ('SIGTERM for graceful shutdown' plus 'force kill option' when the schema already labels it SIGKILL), but it costs almost nothing.

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 two-optional-parameter tool with no output schema and no annotations, the description is nearly sufficient: an agent knows what it does and the two termination modes. Only the state-preservation and failure modes are unaddressed, which is acceptable at this complexity level.

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 the schema already documents both parameters, including the side effect that omitting 'name' lists running VMs. The description's mention of SIGTERM and the force-kill option largely restates the schema rather than adding new 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?

The description opens with a specific verb+resource: 'Stop a running QEMU virtual machine.' An agent can immediately tell this is the teardown counterpart to adb_qemu_start, though the description never names that sibling explicitly, leaving the differentiation to inference from the tool name.

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?

Usage is only implied — 'stop a running QEMU virtual machine' suggests you call it on a VM you previously started. There is no explicit statement of when to prefer this over adb_emulator_stop or adb_qemu_disconnect, nor any precondition such as the VM having been started via adb_qemu_start.

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