Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

run_backup_job

Starts a Proxmox backup job now using its configured guests, storage, and mode; Proxmox prunes the result at the job’s next scheduled run.

Instructions

Run a backup job's backup now (its guests, storage and mode), as Run Now does — without its keep: Proxmox prunes at the job's next scheduled run.

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": {
      "host": "<host>",
      "id": "<id>",
      "reason": "<reason>"
    },
    "name": "run_backup_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
hostYesThe host's id, from list_hosts.
reasonYesWhy you are doing this, in a sentence. The user sees it in the approval window and in the log.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, so the description's real contribution is the non-obvious retention consequence: the produced backup has no keep protection and Proxmox will prune it at the job's next scheduled run. That is valuable behavioral context beyond structured fields, though it omits whether the call blocks until the backup finishes.

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 compact sentence with the scope stated up front and the retention caveat following the dash. The phrase 'without its keep' is terse to the point of being cryptic, but nothing is wasted.

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

Completeness3/5

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

For a mutation that triggers a potentially long-running backup with no output schema, the definition should say whether the call returns immediately or waits for completion, and what a failure looks like. The retention caveat is covered, but the execution/latency model is missing.

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 67%: host and reason are documented in the schema, while id is not, and the description does not explain where the job id comes from (presumably list_backup_jobs). The mention of guests/storage/mode describes job configuration, not the parameters, so it adds little parameter meaning.

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 names a specific verb and resource ('Run a backup job's backup now') and clarifies scope via job config ('its guests, storage and mode'). It implicitly distinguishes itself from 'Run Now' behavior by noting the missing keep, though the reference is oblique enough that an agent may not immediately map it to the backup_now sibling.

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?

Usage is implied: run an existing job's backup immediately rather than creating or editing one. However, no explicit alternative is named for the obvious ambiguity with backup_now, and there is no statement of when not to use it (e.g., for ad-hoc guest backups outside a job).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.