Skip to main content
Glama
Sign In
mcp-duplicati

mcp-duplicati

by aaronckj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_backup

Remove a backup job configuration from Duplicati without deleting the actual backup data stored on the destination.

Instructions

Delete a backup job configuration. Does NOT delete backup data on 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": "delete_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
backup_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It clearly states the non-destructive behavior regarding backup data, but it does not mention whether the action is reversible, requires permissions, or affects running backups. Moderate transparency.

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?

Two sentences with no wasted text. The first sentence states the primary action, and the second provides a critical behavioral clarification. Front-loaded structure.

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?

For a simple deletion tool, the description covers purpose and a key behavioral trait, but fails to explain the only parameter. Without schema description or parameter guidance, the tool is incompletely documented for an AI agent.

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

Parameters1/5

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

Schema description coverage is 0%, and the tool description does not explain the backup_id parameter. An AI agent has no additional meaning beyond the parameter name and type to understand what value to provide.

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?

The description clearly states that the tool deletes a backup job configuration and explicitly clarifies that it does NOT delete backup data. This specific verb-resource combo distinguishes it from sibling tools that might delete actual data.

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?

The description implicitly differentiates from tools that delete data, but it does not explicitly name alternatives or provide when-to-use guidance. With many sibling tools like abort_backup or repair_backup, more context would help.

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