Skip to main content
Glama

Get node QEMU capabilities

proxmox_get_node_capabilities
Read-only

Retrieve a Proxmox node's supported QEMU CPU models, machine types/versions, and toggleable CPU flags so you can choose valid CPU and machine options for VM configuration.

Instructions

Get what a node's QEMU supports for VM configuration: CPU models (built-in and custom), machine types/versions (q35, i440fx) and the VM-specific CPU flags that can be toggled. Use it to pick valid values for a VM's cpu/machine options.

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": "proxmox_get_node_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
archNoGuest architecture (default the host's)
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
sectionsNoWhich parts to return (default all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description need not repeat it. The description does add useful behavioural context about what comes back — built-in vs custom CPU models, q35/i440fx machine versions, toggleable flags — which matters because there is no output schema. It says nothing about cost, caching, or whether the output varies by arch, so it is solid but not rich.

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?

Two sentences, front-loaded with what is returned and followed by the intended use. Nothing is redundant with the title, and no filler is present.

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, the description carries the burden of describing the return values, and it does so by naming the three result categories that match the sections parameter. The remaining gap — no indication of result size or how arch affects output — is minor for a small read-only introspection tool with full schema coverage.

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%; node, arch, and the sections enum are all documented in the schema, including the default-node fallback and the pointer to proxmox_list_nodes. The description adds only the loose framing "a node's QEMU" and does not explain, for example, how arch changes the returned capability set. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get what a node's QEMU supports") and enumerates the three concrete result categories: CPU models, machine types, and toggleable VM CPU flags. This distinguishes it from the many neighbouring proxmox_get_node_* tools, which report on configuration, services, or stats rather than QEMU/VM-config capabilities.

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?

The second sentence gives an explicit use case: "Use it to pick valid values for a VM's cpu/machine options." That tells an agent when this tool is appropriate. It does not name an alternative or state when-not to use it, so it falls short of a 5.

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