Skip to main content
Glama
Ruashots

Proxmox MCP Server

by Ruashots

pve_delete_ha_group

Remove a High Availability (HA) group from Proxmox VE infrastructure to manage cluster resources and configurations.

Instructions

Delete HA group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupYesHA group ID
Behavior1/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention if deletion is permanent, requires permissions, affects dependent resources, or has side effects, leaving critical gaps for a destructive operation.

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 extremely concise with two words, front-loading the key action. There is no wasted text, though this brevity contributes to under-specification rather than efficiency.

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

Completeness2/5

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

For a destructive tool with no annotations and no output schema, the description is incomplete. It lacks details on behavior, outcomes, error conditions, or integration with sibling tools, making it inadequate for safe and effective use.

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 description coverage is 100% with one parameter 'group' documented as 'HA group ID'. The description adds no additional meaning beyond this, such as format examples or sourcing. Baseline score of 3 applies since the schema adequately covers the parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete HA group' restates the tool name 'pve_delete_ha_group' with minimal elaboration, making it a tautology. It specifies the verb 'Delete' and resource 'HA group', but lacks detail on what an HA group is or the scope of deletion, failing to distinguish from siblings like 'pve_delete_ha_resource'.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives, prerequisites, or consequences. Sibling tools include 'pve_delete_ha_resource' and 'pve_list_ha_groups', but the description offers no comparison or context for selection.

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/Ruashots/proxmox-mcp'

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