Skip to main content
Glama
Sign In
Proxmox VE MCP Server

Proxmox VE MCP Server

by MTDEV2312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

configure_cloudinit_vm

Configure Cloud-Init settings on Proxmox VMs to automate OS provisioning, including user credentials, SSH keys, network config, and DNS.

Instructions

Configure Cloud-Init settings for automated OS setup.

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": {
      "node": "<node>",
      "vmid": "<vmid>"
    },
    "name": "configure_cloudinit_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYes
vmidYes
citypeNo
ciuserNo
sshkeysNo
cicustomNo
ciupgradeNo
ipconfig0No
ipconfig1No
cipasswordNo
nameserverNo
searchdomainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of explaining behavioral traits. It only states a high-level purpose and fails to disclose what settings are modified, whether the operation is destructive, or if any regeneration is required.

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 description is a single, concise sentence that front-loads the primary action without redundancy. It is structurally sound, but the brevity borders on under-specification given the tool's complexity.

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

Completeness1/5

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

The description is far too sparse for a tool with 12 parameters, no annotations, and no output schema. It lacks information about invocation context, parameter constraints, and relationship to sibling Cloud-Init tools.

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

Parameters1/5

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

The schema has 0% description coverage, and the description does not mention or explain any of the 12 parameters. Parameters like citype, cicustom, and ciupgrade remain undefined, leaving the agent to infer their meaning from names alone.

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?

The description clearly states the action ('Configure Cloud-Init settings') and provides a general context ('automated OS setup'). However, it does not differentiate this tool from sibling tools like get_cloudinit_config_vm or regenerate_cloudinit_vm, which also relate to Cloud-Init.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as whether the VM must exist or be stopped, nor does it reference related operations like get or regenerate Cloud-Init.

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