Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

backup_now

Trigger an immediate Proxmox guest backup in snapshot mode so the guest keeps running; specify host, VMID, reason, and optional storage or protection settings.

Instructions

Back a guest up now (it keeps running in snapshot mode).

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>",
      "vmid": "<vmid>",
      "reason": "<reason>"
    },
    "name": "backup_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.
modeNo
noteNo
vmidYesThe guest's ID (VMID).
reasonYesWhy you are doing this, in a sentence. The user sees it in the approval window and in the log.
storageNo
protectedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare it is a non-readOnly, non-destructive, non-idempotent operation; the description adds that the guest keeps running in snapshot mode, which is genuinely useful behavioral context. But the parenthetical suggests snapshot mode is always used, while the schema exposes suspend and stop modes, leaving that discrepancy unexplained, and nothing is said about the approval flow or what a repeated call does.

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 front-loaded sentence with no filler. Its compactness is efficient, though for a 7-parameter mutation tool that brevity borders on under-specification rather than ideal sizing.

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?

There is no output schema, so the description need not explain returns, and annotations carry the safety profile. Still, for a 7-parameter tool with under-half schema coverage and a mandatory 'reason' that feeds a user-facing approval window, the definition leaves an agent without enough context on parameter behavior and side effects.

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?

With 7 parameters and only 43% schema description coverage, the description needs to compensate and does not. It touches only on snapshot mode implicitly, saying nothing about mode's other enum values, storage, protected, or note, which are undocumented in both places.

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?

States a specific verb and resource ('Back a guest up') plus immediacy ('now'), which distinguishes an on-demand backup from the scheduled-job siblings like create_backup_job. It does not name or explicitly contrast any sibling, so it falls short of a 5.

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?

'now' implies this is for immediate/ad-hoc backups rather than configuring a job, which is useful implied guidance. However, it never states when to choose this over run_backup_job or create_backup_job, and gives no exclusions or prerequisites (e.g. auth or approval requirements).

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