Skip to main content
Glama

adb_qemu_images

List, create, or delete QEMU disk images (qcow2 or raw) for virtual machines, managing storage in the DeepADB image directory.

Instructions

Manage QEMU disk images for virtual machines. List available images, create new qcow2/raw disk images, or delete existing ones. Images are stored in the DeepADB image directory.

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": {
      "action": "<action>"
    },
    "name": "adb_qemu_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoImage name (for create/delete). Alphanumeric, hyphens, underscores only.
actionYesAction to perform
formatNoImage format. qcow2 is recommended (sparse, snapshots). raw for maximum I/O performance.qcow2
sizeMbNoImage size in MB (for create). Default 8192 (8GB). Range: 64-65536.

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

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It identifies create and delete operations but does not disclose whether deletion is irreversible, whether an image in use can be deleted, what permissions are required, or what happens if a named image already exists; for a mutation tool with destructive actions, this is a notable gap.

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?

The description is three short sentences, front-loads the tool's purpose, and avoids unnecessary wording. The final sentence about storage location is useful context, though the action list slightly restates what the schema enum already conveys.

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 four-parameter management tool with no annotations and no output schema, the description covers purpose, actions, and storage location. It is still missing operational context that would help an agent invoke it safely, especially around create/delete preconditions and destructive behavior.

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 input schema already explains name, action, format, and sizeMb in detail. The description adds some context by mentioning qcow2/raw images and the storage directory, but it does not add parameter-specific meaning beyond the schema.

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 clearly states a specific resource, QEMU disk images, and enumerates the supported operations: list, create, and delete. It distinguishes the tool from runtime QEMU tools by focusing on image management, though it does not explicitly name which sibling handles VM setup or startup.

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 description implies usage by listing the three supported actions, so an agent can infer that this is the image-management tool. However, it gives no explicit when-to-use guidance versus siblings such as adb_qemu_setup or adb_qemu_start, and it does not state prerequisites for creating or deleting images.

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