Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

create_container

Create an unprivileged Proxmox container from a template, set resources and networking, and optionally add an SSH public key; the user enters the root password in the approval window.

Instructions

Create an unprivileged container from a template (see list_install_media). Its root password is typed by the USER in Proxmox Controller's window (you never give or see it); an SSH public key can be added.

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": {
      "host": "<host>",
      "hostname": "<hostname>",
      "template": "<template>",
      "reason": "<reason>"
    },
    "name": "create_container"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNodhcp, or like 192.168.1.50/24.
hostYesThe host's id, from list_hosts.
nodeNo
vmidNo
coresNo
startNo
bridgeNo
reasonYesWhy you are doing this, in a sentence. The user sees it in the approval window and in the log.
disk_gbNo
gatewayNo
nestingNo
storageNo
hostnameYes
swap_mibNo
templateYesA template's volid.
memory_mibNo
start_at_bootNo
ssh_public_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only say this is a non-read-only, non-destructive, non-idempotent write. The description adds a behavior the agent could not otherwise know: the root password is typed by the USER in the Proxmox Controller window and is never given or seen by the agent, which prevents a wasted or failed invocation. It omits what happens on partial failure and whether 'start' defaults to true.

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?

Two sentences, front-loaded with the action and immediately followed by the critical password behavior. The parenthetical cross-reference is efficient. Slightly dense but no wasted clauses.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 18-parameter creation tool with no output schema, the description is thin: it never explains whether the container is started, what it returns (vmid?), or what most networking and sizing parameters mean. The password disclosure is high value, but the definition is far from complete for a call this complex.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 18 parameters and only 22% schema description coverage, the description carries a real burden but only clarifies two of them: template (source it from list_install_media) and ssh_public_key (optionally added). The other 16 — ip, gateway, bridge, storage, vmid, cores, memory_mib, disk_gb, start, nesting — get no meaning from the description, so the coverage gap is not compensated.

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 specific verb and resource with scope: 'Create an unprivileged container from a template.' The 'unprivileged' qualifier and the template pointer make it distinguishable from create_vm and create_cloud_vm in substance, though it never names those siblings.

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

Usage Guidelines3/5

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

Provides one concrete precondition — the template volid comes from list_install_media — which is genuine usage guidance. It does not say when to choose a container over create_vm or create_cloud_vm, so the alternative selection is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.