Skip to main content
Glama

proxmox_start_vm

Start a stopped Proxmox VM by providing its node and VM ID, restoring the virtual machine to a running state for workload access.

Instructions

Start a stopped Proxmox VM.

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>",
      "node": "<node>"
    },
    "name": "proxmox_start_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYes
vmidYes
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It conveys only that this is a mutation that starts (not restarts) a stopped VM; it says nothing about required permissions, idempotency, whether the call blocks until boot completes, or whether it returns a task handle.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words, but the brevity is under-specification rather than tight editing; there is room for a second sentence covering preconditions or parameter meaning without bloat.

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

Completeness2/5

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

For a state-changing VM operation with no annotations, no output schema, and zero parameter documentation, one sentence is far too thin. An agent cannot determine argument semantics or the effect/side effects of a successful call from this definition alone.

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

Parameters1/5

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

Schema description coverage is 0% across three parameters, and the description mentions none of them. vmid, node, and especially the optional gateway_id are entirely unexplained, leaving the agent to guess at meaning and whether gateway_id is required for routed access.

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?

"Start a stopped Proxmox VM" gives a specific verb and resource plus a precondition (the VM must be stopped), and the Proxmox qualifier separates it from the vsphere_start_vm and xo_start_vm siblings. It stops short of naming any sibling or stating scope, so it is clear but not fully differentiated.

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?

The only usage signal is the implied precondition that the VM be stopped; there is no statement of when to prefer this over vsphere_start_vm or xo_start_vm, no prerequisites such as node/auth context, and no guidance on what to do if the VM is already running.

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