Skip to main content
Glama

Check VM feature support

proxmox_check_vm_feature
Read-only

Check if a VM’s storage supports snapshots, linked clones, or full copies and which nodes support it, optionally for a specific snapshot, before cloning or snapshotting.

Instructions

Check whether a VM's storage supports snapshots, linked clones ('clone') or full copies ('copy'), optionally for a given snapshot, and on which nodes. Useful before proxmox_clone_vm or taking snapshots.

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": {
      "vmid": "<vmid>",
      "feature": "<feature>"
    },
    "name": "proxmox_check_vm_feature"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode the guest is on. Looked up automatically from the VMID when omitted.
vmidYesVM or container ID (VMID), e.g. 100
featureYesFeature to check
snapnameNoCheck for this snapshot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so safety is covered structurally. The description adds the useful behavioral detail that the answer is node-scoped ("and on which nodes"), but says nothing about result shape or what happens when the feature is unsupported.

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 with zero filler, front-loading what is checked, then the feature variants, then the node dimension, and closing with the use case. Nothing could be removed without losing meaning.

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 read-only pre-flight check with four fully documented params and no output schema, the definition covers purpose, scope and trigger conditions adequately. A brief note on the return shape (per-node support flags) would close the last gap, since no output schema exists to carry 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?

Schema coverage is 100%, so baseline is 3, but the description earns extra credit by glossing the enum: it maps "clone" to linked clones and "copy" to full copies, which the schema's "Feature to check" does not convey. It also clarifies that snapname is optional and scoped to a single snapshot.

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 ("Check whether") and resource ("a VM's storage") and enumerates the three feature values it resolves (snapshot, clone, copy), plus the node dimension. An agent can distinguish it from proxmox_check_container_feature (containers) and from the get_* siblings without opening any schema.

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 frames when to use it: "Useful before proxmox_clone_vm or taking snapshots," tying it to a concrete follow-up action. It stops short of stating when not to use it or naming an alternative check tool for the container/copy cases, so not 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