Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

host_power

Destructive

Shut down or reboot a Proxmox host while shutting down its guests first.

Instructions

Shut down or reboot the host itself (its guests are shut down first).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>",
      "action": "<action>",
      "reason": "<reason>"
    },
    "name": "host_power"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.
nodeNo
actionYes
reasonYesWhy you are doing this, in a sentence. The user sees it in the approval window and in the log.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds the important consequence that all guests are shut down first, which is exactly the kind of blast-radius detail an agent needs beyond the annotations. It omits reversibility and any availability impact on the host itself.

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?

A single well-formed sentence with the destructive consequence front-loaded. There is no filler and every clause carries information.

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

Completeness3/5

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

For a destructive host-level operation with no output schema and half the parameters undocumented, the description covers the critical guest-shutdown consequence but says nothing about the reason/approval workflow, the node parameter, or expected result. It is adequate but leaves meaningful gaps.

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

Parameters2/5

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

The description adds no meaning about any of the four parameters. With only 50% schema description coverage, the undocumented node parameter is left entirely unexplained in both schema and prose, and the description does not compensate for that gap.

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

Purpose4/5

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

The description states a specific pair of verbs (shut down or reboot) against a specific resource (the host itself), which clearly separates it from guest-level operations like guest_power. It stops short of naming sibling tools, but 'host itself' plus 'its guests are shut down first' makes the scope unambiguous.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to choose this over bulk_power or guest_power, no prerequisites, and no note about the approval requirement implied by the reason parameter. The agent can infer that this affects the whole host, but nothing tells it when that is the right call versus a guest-level action.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.