Skip to main content
Glama
Bldg-7

Proxmox MCP Server

by Bldg-7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create LXC Container

proxmox_create_lxc

Create a new LXC container on a Proxmox node using a unique VMID and OS template, with configurable RAM, rootfs, storage, hostname, password, and network settings.

Instructions

Create a new LXC container (requires elevated permissions)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
net0NoNetwork interface config (e.g., name=eth0,bridge=vmbr0,ip=dhcp)
nodeYesNode name where container will be created
vmidYesContainer ID number (must be unique, or use proxmox_get_next_vmid)
memoryNoRAM in MB
rootfsNoRoot filesystem size in GB8
storageNoStorage locationlocal-lvm
hostnameNoContainer hostname
passwordNoRoot password (minimum 5 characters)
ostemplateYesOS template (e.g., local:vztmpl/debian-12-standard_12.2-1_amd64.tar.gz)

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.4/5.0
Behavior3/5

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

Annotations already mark this as not read-only and not idempotent; the description adds the useful auth requirement of elevated permissions. It does not disclose other behavioral context such as whether creation is asynchronous, what resources are consumed, or what happens on validation failure. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence: action and resource first, permission caveat parenthetically. It is efficient, though it forgoes the opportunity to weave in usage guidance without bloat.

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 9-parameter create operation with no output schema, this is minimally adequate: the schema covers all parameter semantics, and the description flags the key permission requirement. It is missing high-level behavioral context such as success output or how a node/template is validated, but it is not misleading.

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%, with rich descriptions and examples for all 9 parameters (e.g., net0 format, vmid uniqueness, ostemplate example). The description adds no parameter-level detail, so it stays at the baseline 3.

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?

Description states a clear action ('Create') and specific resource ('LXC container'), and the qualifier 'LXC' distinguishes it from the sibling proxmox_create_vm. The parenthetical adds a relevant permission constraint without obscuring the purpose.

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?

It provides one prerequisite ('requires elevated permissions') but no guidance on when to choose this tool over alternatives such as proxmox_create_vm or how to determine whether an LXC container vs a VM is appropriate. No exclusions or conditions of use are stated.

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