Skip to main content
Glama
Sign In
mcp-duplicati

mcp-duplicati

by aaronckj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

run_backup

Start a backup immediately by providing the backup ID. Use this to run a backup job on demand.

Instructions

Trigger a backup job to run immediately.

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": "run_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
backup_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states it triggers immediately. It does not disclose side effects (e.g., blocking, performance impact), what happens during backup, or behavior when backup already running.

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 clear sentence with no waste. It is appropriately sized for a simple tool, though could add brief context without losing 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 no output schema and minimal description, the tool lacks completeness. It doesn't explain return value, errors, or integration with sibling tools like 'list_backups' or 'backup_status'. The AI agent lacks sufficient context to use it reliably.

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 coverage is 0%, so description must compensate. It only mentions 'backup_id' without explaining what it refers to (e.g., backup configuration ID or job ID), leaving ambiguity. A simple 'Backup Id' from schema is unhelpful.

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 uses the specific verb 'trigger' and resource 'backup job', clearly indicating an immediate action. It distinguishes from siblings like 'create_backup' (which creates configuration) and 'abort_backup' (which stops).

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?

It implies usage when a backup job exists, but provides no explicit guidance on when to use it vs alternatives, prerequisites, or exclusions. The context among siblings is not leveraged.

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