duplicacy-mcp

Overview Schema Source Related Servers Discussions Admin

Backup status

get_backup_status

Read-onlyIdempotent

Retrieve current state and last-run details for a Duplicacy snapshot—status, exit code, last success, duration, files, and bytes—to monitor one backup across machines or storage targets.

Instructions

Current state and last-run details of one Duplicacy snapshot: running, exit_code (0 = success, null = unknown), last_success (RFC 3339, UTC), duration in seconds, files and bytes. A snapshot backed up to several storage targets or from several machines returns one row each. Get valid IDs from list_snapshots. For a health check across all backups use get_backup_overview instead.

Input Schema

Name	Required	Description
`machine`	No	Only this machine, exactly as list_snapshots returns it in machines, for example "nas". Omit for all.
`snapshot_id`	Yes	Duplicacy snapshot ID, exactly as list_snapshots returns it, for example "photos".
`storage_target`	No	Only this storage target, exactly as list_snapshots returns it in storage_targets, for example "b2". Omit for all.

Output Schema

Name	Required	Description	Default
`count`	Yes
`backups`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.2.1Oct 29, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / machine

Added value: +{
+  "description": "Only this machine, exactly as list_snapshots returns it in machines, for example \"nas\". Omit for all.",
+  "maxLength": 256,
+  "type": "string"
+}

changedInput schema / properties / snapshot_id / description

Previous value: -"The snapshot ID to query status for"New value: +"Duplicacy snapshot ID, exactly as list_snapshots returns it, for example \"photos\"."

addedInput schema / properties / snapshot_id / maxLength
```
Added value: +256
```
addedInput schema / properties / snapshot_id / minLength
```
Added value: +1
```

addedInput schema / properties / storage_target

Added value: +{
+  "description": "Only this storage target, exactly as list_snapshots returns it in storage_targets, for example \"b2\". Omit for all.",
+  "maxLength": 256,
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "backups": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "exit_code": {
+            "description": "Exit code of the last run: 0 is success, anything else is a failure, null means the exporter has not reported one",
+            "type": [
+              "null",
+              "integer"
+            ]
+          },
+          "last_bytes_new": {
+            "description": "New bytes in the last run",
+            "type": "number"
+          },
+          "last_bytes_uploaded": {
+            "description": "Bytes uploaded by the last run",
+            "type": "number"
+          },
+          "last_chunks_new": {
+            "description": "New chunks in the last run",
+            "type": "number"
+          },
+          "last_chunks_size_bytes": {
+            "description": "Compressed size of the chunks the last snapshot references, in bytes",
+            "type": "number"
+          },
+          "last_duration_seconds": {
+            "description": "Duration of the last run, in seconds",
+            "type": "number"
+          },
+          "last_files_new": {
+            "description": "Files new in the last run",
+            "type": "number"
+          },
+          "last_files_size_bytes": {
+            "description": "Logical size of all files in the last snapshot, in bytes",
+            "type": "number"
+          },
+          "last_files_total": {
+            "description": "Files in the last snapshot",
+            "type": "number"
+          },
+          "last_revision": {
+            "description": "Revision number created by the last run",
+            "type": "number"
+          },
+          "last_success": {
+            "description": "Time of the last successful run, RFC 3339 in UTC",
+            "type": "string"
+          },
+          "machine": {
+            "description": "Machine that runs the backup",
+            "type": "string"
+          },
+          "running": {
+            "description": "True while a backup is in progress",
+            "type": "boolean"
+          },
+          "snapshot_id": {
+            "description": "Duplicacy snapshot ID",
+            "type": "string"
+          },
+          "storage_target": {
+            "description": "Storage the snapshot is backed up to",
+            "type": "string"
+          },
+          "total_bytes_uploaded": {
+            "description": "Bytes uploaded since the exporter started counting",
+            "type": "number"
+          }
+        },
+        "required": [
+          "snapshot_id",
+          "storage_target",
+          "machine",
+          "running",
+          "exit_code"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "count": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "backups",
+    "count"
+  ],
+  "type": "object"
+}

First observedv0.1.0Apr 3, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine context beyond that: exit_code semantics (0 = success, null = unknown), RFC 3339 UTC timestamp format, and the row-multiplication behavior when a snapshot spans multiple storage targets or machines. It stops short of stating pagination or volume expectations, which keeps it from a 5.

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?

Four tight sentences, front-loaded with what is returned before the ID-sourcing and alternative-tool guidance. No restatement of the title and no filler; each sentence carries either field semantics or routing information.

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?

Output schema exists, so return shape needn't be re-explained, yet the description still clarifies the ambiguous value encodings (exit_code null, RFC 3339 UTC) that an agent needs to interpret results. With read-only annotations and full schema coverage, nothing material is missing for correct invocation.

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%, so the baseline is 3. The description earns above baseline by explaining that a snapshot backed up to several storage targets or from several machines returns one row each — which is precisely the semantics of the optional machine and storage_target filters, telling the agent why it would narrow them rather than just what they are.

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?

States a specific verb+resource (current state and last-run details of one Duplicacy snapshot) and enumerates the returned fields: running, exit_code, last_success, duration, files, bytes. It also distinguishes itself from list_snapshots (ID source) and get_backup_overview (aggregate health check), so an agent can separate it from siblings without opening schemas.

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?

Gives explicit routing: 'Get valid IDs from list_snapshots' as a prerequisite and 'For a health check across all backups use get_backup_overview instead' as the when-not case with a named alternative. This is exactly the when/when-not/alternative pattern, leaving nothing to inference.

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

Deploy Server