Skip to main content
Glama

adb_qemu_status

Check QEMU VM status to see running VMs, resource usage, port mappings, and KVM/QEMU availability.

Instructions

Show status of QEMU virtual machines — running VMs with resource usage and port mappings, plus KVM and QEMU availability.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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. First observedv1.1.1

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the shape of what gets reported (per-VM resource usage and port mappings, plus KVM and QEMU availability), which implies a non-destructive read. It does not state what happens when KVM/QEMU are absent (empty list vs error), whether elevated permissions or host access are needed, or whether the call is fast or long-running.

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?

A single sentence front-loads the core action and uses an em-dash enumeration to add the payload detail without a second sentence. Every clause carries information an agent would otherwise have to discover by calling the tool.

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?

With no output schema and no annotations, the description usefully describes what the caller will see (VM list, resource usage, port mappings, KVM/QEMU availability), which is the main completeness risk here. Minor gaps remain around error/empty states and permission requirements, but for a zero-argument status probe it covers what an agent needs to select and call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the schema already conveys. Baseline for a 0-parameter tool applies, with no deficiency to penalize.

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 uses a specific verb ('Show status') plus a specific resource ('QEMU virtual machines') and enumerates the payload: running VMs with resource usage and port mappings, plus KVM/QEMU availability. An agent can distinguish it from adb_qemu_start, adb_qemu_stop, adb_qemu_images or adb_qemu_connect because those are lifecycle/artifact tools while this one is purely observational. It does not name any sibling explicitly, which is the only thing keeping it off a 5.

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: an agent can infer 'call this to check whether VMs are up and how much they are consuming' from the described contents. There is no explicit statement about when not to use it, no pointer to adb_qemu_start for launching a missing VM, and no note on whether it is worthwhile when QEMU is not installed. Adequate but with a clear routing gap.

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