Skip to main content
Glama
Sign In
mcp-duplicati

mcp-duplicati

by aaronckj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

verify_backup

Verify backup integrity by comparing local database with data at the destination to detect inconsistencies or corruption.

Instructions

Verify backup integrity by comparing local database with actual data at the destination.

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": {
      "backup_id": "<backup_id>"
    },
    "name": "verify_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
backup_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions a comparison operation but does not state if the tool is read-only, what happens on failure, required permissions, or whether it modifies state. This is insufficient for an agent to predict consequences.

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?

The description is a single, front-loaded sentence that conveys the core action efficiently. However, excessive brevity sacrifices necessary detail, slightly detracting from conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and the complexity of verification, the description lacks critical context: return format, synchronous/asynchronous behavior, and practical interpretation of integrity results. This leaves the agent with significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for parameter semantics. However, it adds no detail about backup_id beyond the schema's existence. No format, constraints, or relationship to other data is provided.

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?

The description clearly states the verb 'verify' and the resource 'backup integrity', and specifies the method (comparing local database with destination data). This distinguishes it from sibling tools like create_backup or delete_backup.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives like repair_backup or backup_status. The description implies a use case but does not explicitly state prerequisites or excluded scenarios.

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