Skip to main content
Glama

Get replication job

proxmox_get_replication_job
Read-only

Retrieve a Proxmox replication job's configuration and digest for safe updates, plus its current status on the source node, by job ID and optional node.

Instructions

Get one replication job's configuration (with digest for safe updates) and its current status on the source node.

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": {
      "id": "<id>"
    },
    "name": "proxmox_get_replication_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesReplication job ID: <guest VMID>-<job number>, e.g. "100-0" (see proxmox_list_replication_jobs)
nodeNoNode the guest currently runs on (the replication source). Looked up from the guest when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.8/5.0
Behavior4/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 still earns credit by disclosing that the response includes a digest usable for safe subsequent updates and that status is reported from the source node, which tells the agent this read has a follow-on mutation use and is node-scoped. It stops short of describing behavior on a missing job or how status is gathered remotely.

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?

A single front-loaded sentence with no filler; the parenthetical about the digest is the only elaboration and it carries real information. Nothing here would be cut without losing meaning.

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 read tool with full schema coverage and no output schema, the description is nearly complete: it says what data comes back (config + status) and hints at the digest linkage to updates. Only error/not-found behavior and the node-omitted path are left unspecified, and the latter is covered by the schema.

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%, with both parameters documented including the ID pattern and the node lookup fallback, so the schema does the heavy lifting. The description only reinforces 'source node' semantics; it adds no extra meaning about ID format or lookup behavior.

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 ('Get one replication job') and names exactly what is returned: configuration plus current status. The word 'one' implicitly separates it from the list sibling, but no alternative is named outright, so it falls just short of explicit sibling differentiation.

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?

Usage is only implied: fetch a single job when you need its config or status, scoped to the source node. There is no explicit when-to-use vs. when-not guidance, no pointer to proxmox_list_replication_jobs for enumeration, and no mention that the node can be omitted (the schema carries that).

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