Skip to main content
Glama
Bldg-7

Proxmox MCP Server

by Bldg-7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Virtual Machine

proxmox_create_vm

Create a QEMU virtual machine on a Proxmox node with a unique VM ID, configuring CPU, memory, disk, network, and ISO options as needed.

Instructions

Create a new QEMU virtual machine (requires elevated permissions)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
isoNoISO image (e.g., "local:iso/alpine-virt-3.19.1-x86_64.iso"), optional
nameNoVM name
net0NoNetwork interface configvirtio,bridge=vmbr0
nodeYesNode name where VM will be created
vmidYesVM ID number (must be unique, or use proxmox_get_next_vmid)
coresNoNumber of CPU cores
memoryNoRAM in MB
ostypeNoOS type (l26=Linux 2.6+, win10, etc)l26
socketsNoNumber of CPU sockets
storageNoStorage location for disklocal-lvm
disk_sizeNoDisk size (e.g., "8G", "10G")8G

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
  2. First observedv1.2.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=false and idempotentHint=false. The description adds the useful auth requirement ('requires elevated permissions') but does not disclose side effects, return value, or behavior when the vmid already exists. No contradiction with annotations.

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 focused sentence with no filler; the core action and the permission caveat are front-loaded. Every word earns its place.

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?

The schema fully covers parameter semantics, and the description adds the critical elevated-permission prerequisite. However, with no output schema and no mention of postconditions (e.g., whether the VM is started or what response is returned), an agent must infer several operational details.

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?

The input schema documents all 11 parameters with descriptions and defaults, so the baseline is 3. The description adds no parameter-level meaning beyond what the schema already provides.

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?

States a clear action and object: 'Create a new QEMU virtual machine'. This tells an agent the tool creates VMs rather than containers or clones, though it does not explicitly name alternatives like proxmox_create_lxc or proxmox_guest_clone.

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

Usage Guidelines2/5

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

No guidance on when to prefer this tool over siblings. The only usage hint is 'requires elevated permissions', which is a prerequisite rather than a selection rule or exclusion.

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