homebutler

by Higangssh

Overview Schema Source Related Servers Discussions Admin

Hybrid

proxmox_guest_reboot

Reboot one explicitly confirmed Proxmox QEMU or LXC guest on a specified node and return the accepted task UPID.

Instructions

Reboot one explicitly targeted Proxmox guest after confirmation and return the accepted task UPID

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": {
      "endpoint": "<endpoint>",
      "node": "<node>",
      "type": "<type>",
      "vmid": "<vmid>",
      "confirm": "<confirm>"
    },
    "name": "proxmox_guest_reboot"
  }
}

Input Schema

Name	Required	Description
`node`	Yes	Proxmox node name
`type`	Yes	Guest type: qemu or lxc
`vmid`	Yes	Proxmox guest VMID from 1 through 999999999
`confirm`	Yes	Must be true to confirm the explicit guest action target
`endpoint`	Yes	Explicit Proxmox endpoint name from config

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.41.0Sep 30, 2026
- addedInput schema / properties / type / enum
```
Added value: +[
+  "qemu",
+  "lxc"
+]
```
Addedv0.23.0Aug 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description adds the important async behavior that the call returns an accepted task UPID rather than completing synchronously, which tells the agent to poll for status. It does not mention the service interruption a reboot causes, leaving a small gap for a disruptive 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?

A single front-loaded sentence with no waste: the action, the targeting constraint, the confirmation prerequisite, and the return value all appear in one compact statement.

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

Completeness4/5

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

With no output schema, the description correctly specifies that an accepted task UPID is returned, which is what the agent needs to know. It could have pointed to proxmox_task_status for polling and noted the downtime implied by a reboot, but nothing required is missing.

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 coverage is 100%, so endpoint, node, type, vmid and confirm are all documented in the schema itself. The description only reinforces the explicit-targeting framing and does not add format or edge-case detail beyond that, so the baseline 3 applies.

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?

States a specific verb (reboot) and a precisely scoped resource (one explicitly targeted Proxmox guest), plus the confirmation gate and return value. It is immediately distinguishable from sibling power tools like proxmox_guest_shutdown and proxmox_guest_start.

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?

"One explicitly targeted" and "after confirmation" convey the conditions for correct invocation, implying the caller must identify a single guest and set confirm. It stops short of naming the alternative tools (shutdown/start) or stating when not to reboot, so it is clear context but not full when/when-not guidance.

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