Skip to main content
Glama
Sign In
Proxmox MCP Server

Proxmox MCP Server

by fredriksknese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

run_backup

Perform an immediate backup of a Proxmox VM using vzdump. Provide the node, VM ID, storage, and optionally set backup mode and compression.

Instructions

Run an immediate backup (vzdump)

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>",
      "storage": "<storage>"
    },
    "name": "run_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoBackup mode: "snapshot", "suspend", or "stop"
nodeYesNode on which to run the backup
vmidYesVM ID to back up
storageYesStorage location for the backup
compressNoCompression algorithm: "zstd", "lzo", or "gzip"

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?

The description provides minimal behavioral context beyond the annotation (destructiveHint false). It does not mention potential blocking, resource usage, whether it overwrites existing backups, or return behavior. With no annotations beyond destructiveHint, more transparency is needed.

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 very short (5 words), which is concise but lacks details that could aid understanding. It is front-loaded with the core action, but the structure could include more context without being verbose.

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 absence of an output schema and the presence of many sibling tools, the description does not explain what happens after running (e.g., task status, cancellation). It assumes prior knowledge of vzdump.

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?

All 5 parameters are described in the schema (100% coverage), so the description adds no additional meaning. The schema already provides sufficient semantics for each parameter.

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?

The description clearly states the action 'Run an immediate backup' and identifies the underlying tool 'vzdump'. It distinguishes from scheduled backups (create_backup_job) by specifying 'immediate', but could be more explicit about what 'immediate' entails.

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 on when to use this tool vs alternatives like create_backup_job. It does not mention prerequisites, frequency, or scenarios where this is appropriate.

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