Skip to main content
Glama

proxmox_stop_vm

Gracefully shut down a running Proxmox VM by supplying its node and VM ID, enabling controlled power-off for maintenance or resource savings.

Instructions

Gracefully shutdown a running 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_stop_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYes
vmidYes
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

C2.6/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 behavioral burden. 'Gracefully' implies an ACPI/soft shutdown rather than a hard power-off, but it does not say whether the call blocks, times out, falls back to a forced stop, is reversible, or what permission level is required.

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

Conciseness4/5

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

A single front-loaded sentence with no filler, which is appropriately tight for the operation. Its brevity is a virtue structurally even though the content is under-specified.

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 mutating tool with no annotations, no output schema, and zero parameter documentation, one sentence is far from sufficient. Nothing tells the agent what a successful shutdown returns or how to handle an already-stopped VM.

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 never mentions any of them. The unexplained 'gateway_id' parameter in particular is left entirely for the agent to guess, so the description compensates for nothing.

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: 'Gracefully shutdown a running Proxmox VM.' The word 'Proxmox' plus 'shutdown' implicitly separates it from siblings like proxmox_start_vm or the vsphere/xo equivalents, though it never explicitly routes agents away from them.

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 word 'running' hints that the target must be powered on, but there is no explicit when-to-use guidance, no mention of prerequisites (node/vmid must be valid, VM must exist), and no statement about alternatives such as a hard stop or restart.

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