Skip to main content
Glama

pve_cloudinit_set

Set cloud-init fields like ciuser, sshkeys, and ipconfig on a Proxmox QEMU guest. Provides a dry-run plan with masked secrets before execution.

Instructions

MUTATION: set cloud-init fields (ciuser/sshkeys/ipconfigN/...) on a QEMU guest — kind='lxc' is refused (cloud-init is QEMU-only). Dry-run by default with secrets masked in the PLAN; confirm=True to execute. Synchronous; the return carries a top-level undo_record key beside status/result (secret fields excluded). Effects apply on next reboot + cloud-init regen, not live. Read current values with pve_cloudinit_get.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoGuest type; cloud-init applies to `qemu` guests.qemu
nodeNoPVE node the guest runs on. Omit to resolve it automatically from the cluster.
vmidYesNumeric VMID of the QEMU guest to set cloud-init config on.
changesYesCloud-init fields to change, e.g. {'ciuser': 'admin', 'sshkeys': '...', 'ipconfig0': 'ip=dhcp'}.
confirmNoLeave `false` (default) to get a dry-run PLAN with secrets masked; set `true` to execute.
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?

Despite no annotations, the description fully discloses behavior: mutation, dry-run with masked secrets, synchronous execution, undo_record in return, effect on next reboot, and non-live update.

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 long sentence but is front-loaded with key purpose and packs essential information efficiently. Minor improvement could be to break into shorter sentences.

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?

With an output schema present, the description covers all critical aspects: behavior, parameters, return structure, and effect timing, leaving no significant gaps.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds value by listing example fields, explaining confirm behavior, and noting kind restriction, going beyond what the schema provides.

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 it sets cloud-init fields on QEMU guests, lists example fields, and explicitly refuses LXC, distinguishing it from other tools.

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?

Provides clear usage guidance: use for QEMU cloud-init, not for LXC; defaults to dry-run, confirm to execute; recommends reading current values with pve_cloudinit_get.

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