pve-mcp

pve_guest_power

Changes a Proxmox guest's power state and waits for completion, supporting start, stop, shutdown, reboot, reset, suspend, and resume; stop/reset require confirm=true.

Instructions

Change a guest's power state and wait for it to finish. stop and reset are hard (need confirm=true); shutdown is a clean ACPI/init shutdown.

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": {
      "vmid": "<vmid>",
      "action": "<action>"
    },
    "name": "pve_guest_power"
  }
}

Input Schema

Name	Required	Description	Default
`vmid`	Yes
`wait`	No
`action`	Yes
`confirm`	No
`timeout`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations present the description carries the full burden, and it does deliver the most important behavioral facts: the call blocks until the state change finishes, stop/reset are destructive and gated by confirm=true, and shutdown is a graceful ACPI/init shutdown. It leaves gaps around restart/reboot semantics, suspend/resume, and failure/timeout behavior, which is why it is a 4 rather than 5.

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?

Two tight sentences, zero filler, with the purpose stated first and the confirm/shutdown distinction front-loaded immediately after. Every sentence earns its place.

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?

An output schema exists, so return values need no explanation, and the safety profile of destructive actions is covered. However, for a five-parameter, zero-coverage, unannotated mutation tool, the meaning of wait and timeout and the reboot/reset distinction are missing.

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?

Schema description coverage is 0% across five parameters, so the description must compensate, yet it explains only confirm (indirectly, via the stop/reset rule) and alludes to wait ("wait for it to finish"). The vmid, timeout, and the meaning of the action enum values (e.g. reboot vs reset) remain undocumented.

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?

States a specific verb and resource ("Change a guest's power state") and adds the wait-for-completion scope. It does not name any sibling, but the power-state domain is distinct enough from pve_create_guest/pve_destroy_guest/pve_guest_config that an agent can route correctly.

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

Usage Guidelines3/5

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

Usage is only implied: the definition tells the agent when confirmation is needed but never says when to prefer this over pve_destroy_guest (for removal) or pve_guest_config (for settings), nor when shutdown should be chosen instead of stop. No explicit when-not guidance.

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