Skip to main content
Glama

Get replication log

proxmox_get_replication_log
Read-only

Read a replication job's last-run log from its source node to diagnose failures and inspect job activity.

Instructions

Read the log of a replication job's last run from the source node, e.g. to diagnose a failing job.

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_log"
  }
}

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.
limitNoMaximum lines (default 500)
startNoFirst line to return (default 0)

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 adds two behavioral facts not in annotations: the log is fetched from the source node, and it covers only the last run rather than history.

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 sentence with zero filler; the resource and retrieval scope come first and the use case trails as a qualifier.

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 four-parameter read tool with full schema coverage and a clear read-only annotation profile, the description covers what the log represents and where it comes from. Minor gaps (no mention of line-based paging behavior at a glance) are already handled 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%, so the id pattern, node lookup, limit, and start offset are all documented in the schema. The description's 'from the source node' echoes the node parameter rather than adding new semantics, so baseline 3 applies.

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?

Names a specific verb and resource: read the log of a replication job's last run. 'Replication job' narrows it enough to separate it from sibling log tools like proxmox_get_cluster_log or proxmox_get_task_log, though it never explicitly names an alternative.

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?

Provides one concrete use case ('e.g. to diagnose a failing job'), which implies when to reach for it. It gives no exclusions or explicit routing between this and proxmox_get_replication_job / proxmox_get_task_log, so usage is suggested rather than 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