Skip to main content
Glama
Sign In
Proxmox VE MCP Server

Proxmox VE MCP Server

by MTDEV2312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

pause_vm

Pause a running QEMU virtual machine on Proxmox VE node. Temporarily halt VM execution while preserving its state.

Instructions

Pause execution of a running QEMU virtual machine.

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": "pause_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYes
vmidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('Pause execution') without elaborating on reversibility, state preservation, or side effects. For a non-destructive operation, this is minimal but not sufficient for an agent to infer safety or post-conditions.

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?

The description is a single, unambiguous sentence with the verb and resource front-loaded. Every word earns its place, with no filler or repetition. It is appropriately minimal for such a straightforward operation.

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?

Given the simple nature of the tool, the description could still mention key contextual details like 'state is preserved and can be resumed with resume_vm' or 'the VM must be running'. With no output schema and no annotations, the description leaves the agent under-informed about the operation's full behavior and lifecycle.

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% and the description does not mention 'node' or 'vmid' at all. Both parameters are undocumented beyond their names and types, leaving the agent to guess their meaning (e.g., what 'node' refers to). The description provides zero additional parameter semantics.

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 ('Pause') and resource ('running QEMU virtual machine'), clearly distinguishing it from sibling tools like stop_vm or resume_vm. It immediately conveys the tool's function without ambiguity.

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?

The description implies the tool should be used on a 'running' VM, which gives some usage context. However, it does not explain when to prefer pause over stop/shutdown/suspend or mention alternatives, leaving the decision partially unclear.

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