Skip to main content
Glama
Higangssh

homebutler

by Higangssh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

proxmox_guest_reboot

Reboot a specified Proxmox QEMU or LXC guest after confirmation and return the accepted task UPID.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYesProxmox node name
typeYesGuest type: qemu or lxc
vmidYesProxmox guest VMID from 1 through 999999999
confirmYesMust be true to confirm the explicit guest action target
endpointYesExplicit Proxmox endpoint name from config

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.41.0
    • addedInput schema / properties / type / enum
      Added value: +[
+  "qemu",
+  "lxc"
+]
  2. Addedv0.23.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It discloses the confirmation requirement and the return of a task UPID, but fails to warn that reboot is disruptive (downtime, service interruption) or state prerequisites such as the guest being running or required permissions.

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 that states the action, the constraint, and the return value without any wasted words. Appropriate size for the tool.

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?

Schema is complete and the description supplies the return value (accepted task UPID) and confirmation condition. However, for a destructive reboot with no annotations or output schema, it should also disclose safety/downtime or prerequisite information; those gaps remain.

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%, so all five parameters are fully documented in the schema. The description adds only the notion of explicit targeting and confirmation, which maps to the confirm parameter without adding syntax or format details beyond the schema.

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: 'Reboot one explicitly targeted Proxmox guest'. The scope (one guest, explicitly targeted) is clear and distinguishes it from a bulk operation, though it does not name sibling alternatives like proxmox_guest_shutdown or 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 Guidelines3/5

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

Implies usage context: reboot a guest after confirmation and only when explicitly targeted. No when-not conditions or explicit alternatives to shutdown/start are provided, leaving the agent to infer routing from the verb alone.

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

Deploy Server

Other Tools