Skip to main content
Glama

pve_ha_rule_create

Create a Proxmox VE HA rule to constrain resource placement by node-affinity or resource-affinity. Dry-run returns a plan; confirm=True to execute.

Instructions

MUTATION: create an HA rule (the PVE 9 replacement for HA groups). Dry-run by default — the PLAN shows the rule type, resources, and placement effect. rule_type is 'node-affinity' (needs nodes; optional strict) or 'resource-affinity' (needs affinity positive|negative). confirm=True to execute. Synchronous (pmxcfs config write, no UPID). RISK_MEDIUM — constrains CRM placement. View rules with pve_ha_rules_list; change one with pve_ha_rule_update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ruleYesNew HA rule ID (name used to reference this rule).
nodesNoComma-separated node list with optional priority, e.g. 'pve1:2,pve2' — required for rule_type='node-affinity'.
strictNonode-affinity only: if True, resources may run ONLY on the listed nodes (availability risk if all are down).
commentNoFree-text comment stored with the rule.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the change.
disableNoIf True, the rule is created disabled (no effect until enabled).
affinityNo'positive' (keep resources together) or 'negative' (keep resources apart) — required for rule_type='resource-affinity'.
resourcesYesComma-separated HA resource SIDs the rule applies to, e.g. 'vm:100,ct:101'.
rule_typeYesRule type: 'node-affinity' (requires nodes) or 'resource-affinity' (requires affinity).
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?

With no annotations, the description fully covers behavior: synchronous operation, pmxcfs config write, no UPID, and RISK_MEDIUM due to CRM placement constraints. It also explains the dry-run and execution flow, ensuring the agent understands the tool's impact.

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 yet comprehensive, front-loading the mutation type and key behavior. Every sentence provides value, including rule types, parameters, and risk level, without unnecessary fluff.

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 complexity of 10 parameters (3 required) and the presence of an output schema, the description is complete. It covers dry-run, rule types, parameter dependencies, risk, and related tools, leaving no critical gaps for an agent to select and invoke the tool correctly.

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?

Although the input schema has 100% description coverage, the description adds significant context, such as explaining rule_type options ('node-affinity' requires nodes; 'resource-affinity' requires affinity), the meaning of 'strict', and the dry-run behavior via 'confirm'. This enriches the agent's understanding beyond the schema.

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 creates an HA rule, mentioning it replaces HA groups. It specifies the mutation type and distinguishes from sibling tools like pve_ha_rules_list for viewing and pve_ha_rule_update for modifying, providing a clear understanding of its purpose.

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?

The description explicitly notes that the tool runs as a dry-run by default and requires confirm=True to execute. It also directs users to view rules with pve_ha_rules_list and change them with pve_ha_rule_update, offering clear guidance on when to use this tool versus alternatives.

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