Skip to main content
Glama
Sign In
Proxmox MCP Server

Proxmox MCP Server

by fredriksknese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_backup_job

Schedule automated backups for VMs with customizable storage, compression, and notification settings.

Instructions

Create a scheduled backup job

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": {
      "schedule": "<schedule>",
      "storage": "<storage>"
    },
    "name": "create_backup_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoBackup mode: "snapshot", "suspend", or "stop"
vmidNoComma-separated list of VM IDs to back up, or "all"
enabledNoWhether the backup job is enabled
storageYesStorage location for backups
compressNoCompression algorithm: "zstd", "lzo", or "gzip"
scheduleYesBackup schedule in cron or systemd timer format
mailnotificationNoEmail notification setting

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

The annotations only provide destructiveHint=false, so the description carries the burden of behavioral disclosure. However, it simply says 'Create a scheduled backup job' without explaining side effects (e.g., whether it modifies existing jobs, requires specific permissions, or any automatic validation). The behavioral transparency is minimal.

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, concise sentence with no wasted words. It is front-loaded. However, it may be too terse, sacrificing helpfulness for brevity. Still, it is well-structured for a simple purpose.

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

Completeness1/5

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

Given the tool has 7 parameters (2 required) and no output schema, the description is severely incomplete. It provides no overview of the backup job lifecycle, no explanation of the 'mode' or 'compress' options, and no mention of response behavior. A user would need to rely entirely on the schema, which lacks high-level context.

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?

Schema coverage is 100%, so each parameter already has a description. The tool description adds no extra meaning beyond what the schema provides. For example, it doesn't elaborate on the 'schedule' format or the impact of 'mode'. Baseline 3 is appropriate.

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 'Create a scheduled backup job', which is a verb+resource. It implies the tool creates a recurring backup job, but doesn't explicitly differentiate it from siblings like 'run_backup' (immediate backup) or 'list_backup_jobs'. However, given the context, the purpose is fairly clear.

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 this tool versus alternatives like 'run_backup' or 'delete_backup_job'. There is no mention of when not to use it or what prerequisites are required (e.g., storage must exist). The description offers no usage context.

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