Skip to main content
Glama

pve_agent_set_password

Set a guest OS user's password inside a Proxmox VM using the QEMU guest agent. Returns a dry-run plan by default; execute with confirm=True to apply the change.

Instructions

MUTATION: set a guest OS user's password via the qemu-agent.

Requires PROXIMO_ENABLE_AGENT=1, the VMID in PROXIMO_AGENT_ALLOWLIST, and a running guest agent inside the VM. Dry-run by default (returns a PLAN); confirm=True executes and returns {"status": "ok", "result": None}. Password is UNCONDITIONALLY redacted from the ledger (fingerprint only — "[redacted]"). Irreversible without knowledge of the old password; no undo primitive on this plane.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoProxmox node name hosting the guest; auto-detected if omitted.
vmidYesNumeric VM ID of the guest whose OS user password is being set.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the password change.
passwordYesNew password for the guest OS user; unconditionally redacted from the ledger.
usernameYesGuest OS username whose password will be changed.
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
Behavior4/5

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

No annotations exist, so the description carries full burden. It explains the mutation, default dry-run, irreversible nature, unconditional password redaction, and prerequisites. It lacks details on error cases or side effects beyond the stated requirements.

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 concise with 5 sentences, front-loading the purpose and using a clean structure. No redundant sentences; every sentence adds value.

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

Completeness4/5

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

Given the presence of an output schema, the description appropriately omits return value details. It covers prerequisites, behavior, and limitations but could address potential error conditions or usage constraints more thoroughly.

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%, so baseline is 3. The description adds context for the password parameter (redaction) but does not significantly enhance understanding of other parameters beyond the schema descriptions.

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 explicitly states the tool sets a guest OS user's password via the qemu-agent, with the verb 'set' and clear resource. It distinguishes itself from siblings like pve_agent_exec or pve_agent_file_read by specifying its unique function.

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

Usage Guidelines4/5

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

The description lists prerequisites (PROXIMO_ENABLE_AGENT=1, allowlist, running agent) and explains the dry-run vs. confirm mode. However, it does not explicitly mention when not to use it or alternatives, leaving some guidance implicit.

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