Skip to main content
Glama

pve_replication_update

Update a PVE replication job with dry-run mode for planning, then execute with confirmation to apply changes.

Instructions

MUTATION: update a PVE replication job. Dry-run by default — the PLAN captures current config for manual revert; confirm=True to execute and returns synchronously (no task UPID). Config-only; in-flight replication is not immediately disrupted. To create a new job use pve_replication_create; to remove one use pve_replication_delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rateNoNew bandwidth limit in MB/s; omit to leave unchanged.
rep_idYesID of the existing replication job to update.
commentNoNew free-text note; omit to leave unchanged.
confirmNoGate: false returns a dry-run PLAN, true executes the update.
disableNoWhether the job is disabled; omit to leave unchanged.
scheduleNoNew Proxmox calendar-event schedule string; omit to leave unchanged.
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?

With no annotations, the description fully discloses mutation behavior, dry-run/confirm semantics, synchronous return, and config-only scope. No contradictions.

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?

Concise single paragraph with all critical information front-loaded (mutation, dry-run, confirm, sync, no disruption). No unnecessary words.

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 100% schema coverage, existence of output schema, and absence of annotations, the description covers behavioral, usage, and parameter context adequately. No missing aspects.

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 100%, so baseline is 3. The description adds little beyond the schema's parameter descriptions; it only mentions 'captures current config for manual revert' which is linked to confirm, but does not significantly enhance understanding.

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 clearly states 'update a PVE replication job' and distinguishes from siblings by naming pve_replication_create and pve_replication_delete for creation and removal.

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

Usage Guidelines5/5

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

Explicitly describes dry-run by default, how to execute with confirm=True, and notes that in-flight replication is not disrupted. Provides when-not guidance by referencing sibling tools.

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