Skip to main content
Glama

pve_disk_resize

Grow a guest disk by specifying a size delta (e.g., '+10G'). Dry-run by default; set confirm=true to execute the resize.

Instructions

MUTATION: grow a guest disk (e.g. size='+10G'). GROW ONLY — a shrink is refused as destructive, and an ambiguous absolute size is refused too unless the current size can be verified first. Dry-run by default; confirm=True to execute. Async — returns a task UPID (poll with pve_task_status). To move a disk to different storage instead use pve_disk_move.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
diskYesDisk key to resize, e.g. `scsi0` or `rootfs`.
kindNoGuest type: `lxc` for a container or `qemu` for a VM.lxc
nodeNoPVE node the guest runs on. Omit to resolve it automatically from the cluster.
sizeYesNew size, as a grow-only delta like `+10G` (shrinking is refused as destructive).
vmidYesNumeric ID of the guest — VMID for a QEMU VM or CTID for an LXC container.
confirmNoLeave `false` (default) to get a dry-run PLAN; set `true` to execute the resize.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses mutation, grow-only constraint, dry-run default, async nature with task UPID, and behavior for ambiguous absolute sizes. All key behavioral traits are covered.

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?

Description is concise (4 sentences), every sentence adds value. It starts with the core action and then covers constraints, options, and alternatives without redundancy.

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

Completeness5/5

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

Given the tool's complexity (mutation, async, dry-run, size constraints) and the presence of an output schema, the description covers purpose, constraints, confirmation flag, async behavior, and a clear sibling alternative. It also notes polling with pve_task_status.

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 coverage is 100% with detailed parameter descriptions. The description adds little beyond the schema (e.g., size example '+10G'). Baseline 3 is appropriate as the schema already documents parameters well.

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 purpose: 'grow a guest disk'. It uses a specific verb-resource pair and distinguishes from a sibling tool (pve_disk_move) by mentioning it for moving disks instead.

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

Usage Guidelines5/5

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

Explicitly states when to use (for growing disks), when not to use (shrinking is refused), and provides an alternative (pve_disk_move for moving storage). Also explains the dry-run vs. confirm behavior.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server