Skip to main content
Glama

pve_replication_create

Define a Proxmox replication job for VM data synchronization across nodes. Dry-run plans changes; confirm executes.

Instructions

MUTATION: create a PVE replication job. Dry-run by default; confirm=True to execute and returns synchronously (no task UPID) — additive, no existing data affected. rep_type is typically 'local'. To modify an existing job use pve_replication_update; to remove one use pve_replication_delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rateNoBandwidth limit in MB/s; omit for unlimited.
rep_idYesUnique ID for the new replication job.
targetYesTarget node (or node/storage) to replicate to.
commentNoFree-text note stored on the job.
confirmNoGate: false returns a dry-run PLAN, true executes the creation.
disableNoIf true, create the job in a disabled state.
rep_typeYesReplication job type, typically 'local'.
scheduleNoProxmox calendar-event schedule string; omit for the default cadence.
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
Behavior4/5

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

With no annotations, the description discloses important behavior: dry-run by default, confirm gate, synchronous return without UPID, and additive nature. It does not mention potential side effects or prerequisites.

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?

The description is extremely concise: two sentences plus a sibling reference. Every sentence adds essential information without redundancy.

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?

Given the output schema exists and parameter descriptions are complete, the description covers key behavioral aspects and usage context. It does not detail return values, but that is handled by the output schema.

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?

All 9 parameters have descriptions in the schema (100% coverage). The description adds context: 'rep_type is typically local' and clarifies the confirm parameter's effect, which adds value beyond the schema.

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?

The description explicitly states 'MUTATION: create a PVE replication job' with specific verb and resource. It also differentiates from siblings by naming update and delete alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear guidance on when to use this tool (create) and when to use alternatives (update, delete). It explains the dry-run default and confirm flag but does not explicitly state 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