Skip to main content
Glama
Sign In
Proxmox VE MCP Server

Proxmox VE MCP Server

by MTDEV2312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

resize_vm_disk

Increase the capacity of a virtual machine disk in Proxmox VE. Specify node, VM ID, disk, and new size to extend storage.

Instructions

Extend the capacity of a virtual machine disk.

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>",
      "disk": "<disk>",
      "size": "<size>"
    },
    "name": "resize_vm_disk"
  }
}

Input Schema

NameRequiredDescriptionDefault
diskYes
nodeYes
sizeYes
vmidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior1/5

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

No annotations are provided, so the description carries full burden. 'Extend the capacity' only states the action, with no disclosure of side effects, irreversibility, permission requirements, or impact on the VM. This is insufficient for a mutation tool.

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, literally concise sentence that directly states the tool's purpose. There is no fluff or redundant information; every word earns its place.

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?

This is a potentially risky mutation tool with 4 required parameters, no annotations, and no output schema. The description fails to provide prerequisites, effects, execution behavior, or return value expectations. A single sentence cannot make the tool safely usable by an agent.

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?

Schema has zero description coverage (0%) and the description doesn't explain any parameter. It implies 'size' relates to capacity but doesn't explicitly map node, vmid, disk, or size. The parameter names are somewhat self-explanatory, but the description adds no syntactic or semantic detail.

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 'Extend the capacity of a virtual machine disk' uses a specific verb ('extend') and clearly identifies the resource (VM disk). It distinguishes from sibling tools like add_vm_disk (adding a new disk) and move_vm_disk, as well as resize_container_disk for containers.

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?

The description implies the tool is for increasing VM disk capacity, but it doesn't explicitly state when to use it over alternatives or exclude other operations (e.g., shrinking, container disks). No mention of alternatives or when-not-to-use, so guidance is implied rather than explicit.

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