Skip to main content
Glama
Sign In
Proxmox VE MCP Server

Proxmox VE MCP Server

by MTDEV2312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

suspend_vm

Suspend a virtual machine by providing node and VM ID, with an option to save state to disk for later resume.

Instructions

Suspend virtual machine state to disk.

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": {
      "node": "<node>",
      "vmid": "<vmid>"
    },
    "name": "suspend_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYes
vmidYes
todiskNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 burden of behavioral disclosure, but it only states 'to disk.' It does not reveal what happens to the VM state, whether resources are released, if a resume operation is required, or any side effects such as potential data loss or network disconnection.

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?

The description is a single, front-loaded sentence with no wasted words. It is concise, but the extreme brevity contributes to the lack of behavioral detail and parameter context.

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 tool with no annotations, no output schema, and minimal parameter documentation, the description is not complete enough. It omits suspend behavior implications, relationship to resume, and how todisk affects operation, leaving the agent to guess important details.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain any of the three parameters. While node and vmid are self-explanatory from their names and types, the todisk boolean (default true) is not described, yet it is critical to understanding the tool's behavior.

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?

The description uses a specific verb ('Suspend') and resource ('virtual machine state') and adds the key qualifier 'to disk,' which distinguishes it from sibling tools like pause_vm, stop_vm, and shutdown_vm. This is a clear, unambiguous statement of the tool's core function.

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?

No guidance is provided on when to use suspend_vm versus alternatives such as stop_vm, shutdown_vm, or pause_vm. The description does not mention prerequisites, effects on running workloads, or how this differs from a full stop or a pause.

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