Skip to main content
Glama
Sign In
Proxmox VE MCP Server

Proxmox VE MCP Server

by MTDEV2312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

regenerate_cloudinit_vm

Regenerate the Cloud-Init drive image for a Proxmox VM to reapply initialization settings or resolve boot issues. Specify the node and VM ID to rebuild the drive.

Instructions

Regenerate the Cloud-Init drive image for a VM.

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": "regenerate_cloudinit_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYes
vmidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states the action without explaining side effects (e.g., overwriting the drive, required VM state, irreversibility). This is insufficient for a mutating operation.

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?

The description is a single, clear sentence with no redundant words. It is front-loaded and efficient, though under-specified in other dimensions.

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?

Given the tool's mutating nature and lack of annotations/output schema, the description is too sparse. It omits return values, required preconditions, and side effects, making it incomplete for safe invocation.

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?

Schema description coverage is 0%, so the description should compensate. It does not mention 'node' or 'vmid' at all, providing no additional meaning beyond the schema's type/required fields.

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?

The description clearly states the tool's function: 'Regenerate the Cloud-Init drive image for a VM.' It uses a specific verb ('regenerate') and resource ('Cloud-Init drive image'), distinguishing it from sibling tools like configure_cloudinit_vm and get_cloudinit_config_vm.

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 (e.g., VM stopped), scenarios where regeneration is appropriate, or contrast with configure/get cloudinit tools.

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