homebutler

Overview Schema Source Related Servers Discussions Admin

proxmox_guest_start

Start an explicitly targeted Proxmox VM or LXC guest after confirmation and return the accepted task UPID for tracking the operation.

Instructions

Start 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_start"
  }
}

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

A3.8/5.0

Behavior4/5

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

Annotations (readOnlyHint=false, destructiveHint=false) are consistent and already cover the safety profile. The description adds real value beyond them by disclosing that the call is asynchronous — it returns an accepted task UPID rather than the final power state — which is non-obvious for a start 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?

One sentence, zero filler, with the target-scope and confirmation constraints front-loaded before the return behavior.

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 five required params and no output schema, the description must carry return semantics, and it does by naming the accepted task UPID. It stops short of telling the agent to poll proxmox_task_status for completion, which is the one piece an agent still has to infer.

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 documented in the schema; baseline is 3. The description reinforces the targeting semantics of the confirm flag but adds no format or constraint detail beyond what the schema already provides.

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 (Start) and resource (Proxmox guest) with a scope qualifier ('one explicitly targeted guest'), which cleanly separates it from proxmox_guest_shutdown and proxmox_guest_reboot. It never names those siblings explicitly, so the differentiation is inferable rather than stated.

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?

'after confirmation' and 'explicitly targeted' imply the precondition for calling, but there is no explicit when-to-use/when-not guidance and no pointer to the stop/reboot alternatives. Usage is suggested rather than spelled out.

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