Skip to main content
Glama

pve_ha_resource_add

Add a guest (VM/CT) to Proxmox HA management. Dry-run returns a plan showing the SID, group, and initial state; set confirm=True to execute.

Instructions

MUTATION: add a guest to HA management. Dry-run by default — the PLAN shows the SID, group, initial state, and blast radius (state='stopped' is HIGH: CRM will stop the guest). confirm=True to execute. Synchronous (pmxcfs config write; CRM enforces state asynchronously) — typically returns null, not a UPID. To remove HA management use pve_ha_resource_remove.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoGuest type: 'lxc' or 'qemu'.lxc
vmidYesNumeric VMID/CTID of the guest to add to HA management.
groupNoHA group to assign (PVE 8 only; PVE 9 removed groups in favor of HA rules — omit on PVE 9).
stateNoDesired HA state, e.g. 'started', 'stopped', 'disabled' ('stopped' has the CRM stop the guest).
confirmNoFalse (default) returns a dry-run PLAN only; True executes the change.
max_restartNoMax number of restart attempts the CRM makes before giving up.
max_relocateNoMax number of relocation attempts the CRM makes before giving up.
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 present, so description carries full burden. Details dry-run plan contents, synchronous write with asynchronous CRM enforcement, and null return. Discloses blast radius for state='stopped'.

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?

Concise, front-loaded, every sentence provides unique information. No redundant text.

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?

Covers purpose, usage, dry-run behavior, return value, undo operation, and version-specific parameter notes. Adequate for a complex HA mutation tool.

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

Parameters5/5

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

Schema coverage is 100%. Description adds context beyond schema: state='stopped' implication, group PVE version differences, and plan components. Adds real value.

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?

Starts with "MUTATION: add a guest to HA management", clearly stating the action and resource. Explicitly distinguishes from sibling pve_ha_resource_remove.

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?

Explains dry-run default and confirm=True to execute. Mentions remove sibling for undo. Lacks explicit comparison to other HA tools like pve_ha_rule_create, but provides sufficient context for typical use.

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