Skip to main content
Glama

pmg_backup_create

Create a Proxmox Mail Gateway configuration backup. Dry-run returns a plan; confirm to execute and save a .tar.gz file to the default backup directory.

Instructions

MUTATION (LOW): create a PMG configuration backup. Dry-run by default. confirm=True to execute. Needs PROXIMO_PMG_* config.

Additive — writes a new backup .tar.gz to /var/lib/pmg/backup/ on the target node; does not touch existing backups or live config. Dry-run returns a PLAN; confirm=True executes and returns {"status": "ok", "result": ...}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPMG node name; defaults to the configured node.
notifyNoNotification mode: always|error|never (default never).never
confirmNoFalse (default) returns a dry-run PLAN; True executes the mutation.
statisticNoWhether to include mail statistics in the backup (default True).
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations exist, so description carries full burden. It discloses mutation type (LOW), additive nature, file location, non-destructive to existing data, dry-run vs execution outputs, and config requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly written sentences, front-loaded with core purpose and mutation level. Every clause adds value with no redundancy.

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

Completeness5/5

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

Given the tool's moderate complexity (5 optional params, no required), the description comprehensively covers purpose, behavior, prerequisites, and outputs for both dry-run and execution modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with per-parameter descriptions. Description adds context beyond schema: confirms dry-run default (confirm param), mentions config requirement (proximo_target context), and explains return types for both modes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it creates a PMG configuration backup, with details on dry-run and execution behavior. Among pmg_* siblings, no other backup creation tool exists, so differentiation is inherent.

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?

Describes prerequisite (needs PROXIMO_PMG_* config) and default dry-run behavior, but does not explicitly contrast with alternative tools or specify when NOT to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server