Skip to main content
Glama

Get guest import metadata

proxmox_get_import_metadata
Read-only

Inspect an importable VM or OVA/OVF source to see suggested creation parameters, disks, NICs, and warnings before creating it in Proxmox VE.

Instructions

Read what Proxmox recognises in an importable guest: a VM on an ESXi storage (volume like "esxi1:ha-datacenter/datastore1/web01/web01.vmx") or an OVA/OVF appliance on a storage with import content ("local:import/appliance.ova"). Find them with proxmox_list_storage_content content=import. Returns the source type, the parameters Proxmox suggests for creating the VM (create_args), the disks and NICs found and warnings about anything that won't carry over (a running source VM, lost EFI state, an OVA that has to be extracted first). Nothing is changed; create the VM with proxmox_import_vm. Proxmox VE 8.2+ (OVA/OVF 8.3+).

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": {
      "volume": "<volume>"
    },
    "name": "proxmox_get_import_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
volumeYesImportable guest, e.g. "esxi1:ha-datacenter/datastore1/web01/web01.vmx" or "local:import/appliance.ova" (see proxmox_list_storage_content content=import)
storageNoStorage ID; taken from the volume ID's prefix when omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this with "Nothing is changed" plus a useful inventory of what comes back (source type, create_args, disks, NICs, warnings). It goes beyond annotations by naming failure modes that surface as warnings (running source VM, lost EFI state, OVA needing extraction). It does not address the idempotentHint=false annotation, which is counterintuitive for a pure read, leaving a small unexplained 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?

Front-loaded with the core action and examples, then return contents, then the follow-up tool and version gate. It is a single dense paragraph rather than a list, which makes the return-value inventory slightly harder to scan, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 return values and does so concretely (source type, create_args, disks, NICs, warnings). Combined with the version requirement and the pointer to the follow-up mutation tool, an agent has everything needed to call it and interpret the result.

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 the baseline is 3, but the description adds real meaning: it shows the exact volume ID shape for both ESXi and OVA sources and explains that storage is derived from the volume ID prefix when omitted. That is more than the schema's terse field descriptions convey.

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 ("Read what Proxmox recognises in an importable guest") and immediately scopes it to two concrete source kinds with literal volume examples. It is clearly distinguishable from proxmox_list_storage_content (discovery) and proxmox_import_vm (the mutation that follows).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: find candidates with proxmox_list_storage_content content=import, and perform the actual creation with proxmox_import_vm. It also states the precondition (Proxmox VE 8.2+, OVA/OVF 8.3+), which is a real gating condition for calling it.

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