Skip to main content
Glama
Sign In
mcp-duplicati

mcp-duplicati

by aaronckj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

search_backup_files

Search for specific files within a backup version using glob patterns. Filter by file name or select a restore time to locate files from a particular snapshot.

Instructions

Search files within a backup version. path_filter: glob pattern (e.g., '*.pdf'). restore_time: 'latest' or ISO timestamp.

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

Input Schema

NameRequiredDescriptionDefault
backup_idYes
path_filterNo*
restore_timeNolatest

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, and the description only states it searches files. It does not disclose whether the operation is destructive or read-only, nor does it mention authentication, rate limits, or side effects. For a tool with no annotation coverage, this is insufficient behavioral context.

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: the first states the purpose, the second adds parameter semantics. No redundant information. Every word earns its place, and the structure is front-loaded.

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 3 parameters, no output schema, and no annotations, the description should cover all parameters and behavioral traits. It fails to explain backup_id or describe the return format (e.g., list of files). A search tool needs input guidance and output expectations, which are missing.

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

Parameters3/5

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

The schema has 0% description coverage, so the description must compensate. It explains path_filter as a glob pattern and restore_time as 'latest' or ISO timestamp, but omits any details for the required backup_id parameter. This adds some value but leaves a gap.

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 the tool's purpose: 'Search files within a backup version.' This is a specific verb+resource combination that distinguishes it from sibling tools like list_backups or restore_files. The additional parameter hints further clarify its scope.

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 implies usage for searching files within a backup version but provides no explicit guidance on when to use it versus alternatives like restore_files or list_versions. No exclusions or prerequisites are mentioned, leaving the agent to infer context.

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