Skip to main content
Glama

Get backup defaults

proxmox_get_vzdump_defaults
Read-only

Show the backup defaults a Proxmox VE node applies—storage, mode, compression, retention, and bandwidth—then merge a storage's settings to clarify expected backup behavior.

Instructions

Show the vzdump defaults a node applies to backups (from /etc/vzdump.conf, merged with a storage's settings when storage is given): default storage, mode, compression, retention, bandwidth limits and so on.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_get_vzdump_defaults"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
storageNoInclude this storage's settings (e.g. its retention)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine context about data provenance and merge behavior with a storage, but says nothing about what happens when /etc/vzdump.conf is absent, whether values are resolved or raw, or how errors surface.

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?

One sentence, front-loaded with the core action and resource, with the source and merge condition trailing as useful qualifiers. The trailing 'and so on' is slightly loose but costs little.

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

Completeness4/5

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

For a two-parameter, optional-params read tool with no output schema, the description covers the source of the data, the merge behavior, and the kinds of values returned (storage, mode, compression, retention, bandwidth). The main omission is any indication of the return shape or how node defaulting resolves at the top level, though the schema covers node defaulting.

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 description coverage is 100%, and both parameters (`node`, `storage`) are already documented in the schema, including the storage example about retention. The description largely restates the merge effect already implied by the schema, so it adds little new parameter meaning beyond the baseline.

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 uses a specific verb ('Show') plus a precise resource ('the vzdump defaults a node applies to backups') and names the underlying source (/etc/vzdump.conf merged with storage settings). That is clear enough to separate it from job- or config-specific siblings conceptually, though it never names an alternative tool outright.

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 explains how the `storage` parameter changes behavior ('merged with a storage's settings when `storage` is given'), but it gives no guidance on when to use this instead of proxmox_get_backup_config or proxmox_get_backup_job, and no prerequisites or exclusions are stated.

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