Skip to main content
Glama
GeiserX

duplicacy-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

List snapshots

list_snapshots
Read-onlyIdempotent

Lists every reported snapshot ID, storage target, and machine in sorted order so you can obtain valid values for filtering backups in other tools.

Instructions

Every snapshot ID, storage target and machine the exporter reports, sorted. backups lists each snapshot_id, storage_target and machine combination. Call this first to get valid values for the snapshot_id, storage_target and machine arguments of the other tools.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYesNumber of snapshot IDs
backupsYesEvery snapshot_id, storage_target and machine combination with backup metrics
machinesYesEvery machine seen, sorted
snapshot_idsYesEvery snapshot ID the exporter has seen, sorted
storage_targetsYesEvery storage target seen, sorted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "backups": {
+      "description": "Every snapshot_id, storage_target and machine combination with backup metrics",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "machine": {
+            "type": "string"
+          },
+          "snapshot_id": {
+            "type": "string"
+          },
+          "storage_target": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "snapshot_id",
+          "storage_target",
+          "machine"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "count": {
+      "description": "Number of snapshot IDs",
+      "type": "integer"
+    },
+    "machines": {
+      "description": "Every machine seen, sorted",
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "snapshot_ids": {
+      "description": "Every snapshot ID the exporter has seen, sorted",
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "storage_targets": {
+      "description": "Every storage target seen, sorted",
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    }
+  },
+  "required": [
+    "snapshot_ids",
+    "count",
+    "backups",
+    "storage_targets",
+    "machines"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that results are sorted and that the payload is exposed under a 'backups' key, which annotations cannot convey. It stops short of noting cost or volume, hence a 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the resource and return fields in the first sentence, and the call-ordering advice comes last where it belongs. The middle sentence ('backups lists each snapshot_id, storage_target and machine combination') largely restates the first, costing a little density.

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?

With an output schema present, return values need not be detailed, and the description still names the key fields and the 'backups' container. A zero-arg read tool with annotations fully covered needs no more than this.

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?

Zero parameters, so there is nothing to disambiguate; baseline 4 applies. The description correctly frames the tool as an unfiltered enumeration, which reinforces that no arguments are accepted.

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 resource (snapshots) and the exact fields returned (snapshot ID, storage target, machine), plus ordering. It is clearly distinguishable from the get_* siblings, which return status/overview rather than the raw enumerated set.

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 says 'Call this first to get valid values for the snapshot_id, storage_target and machine arguments of the other tools' — a concrete ordering rule plus the reason. No alternatives are left 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

Other Tools