Skip to main content
Glama
MCP Dokploy Online
by igoruam

backup-listBackupFiles

Read-onlyIdempotent

List backup files for a specified backup destination, optionally filtered by server and narrowed by a search term, to inspect available backups.

Instructions

GET /backup.listBackupFiles

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": {
      "destinationId": "<destinationId>",
      "search": "<search>"
    },
    "name": "backup-listBackupFiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchYes
serverIdNo
destinationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: no note on whether results are paginated, whether 'search' is a substring or exact match, or whether an unknown destination errors or returns empty.

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

Conciseness2/5

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

It is short, but brevity here comes from under-specification rather than efficiency; a route string is not a useful front-loaded summary for an agent choosing among many backup-related siblings.

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

Completeness1/5

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

For a three-parameter list tool with zero schema documentation and no output schema, the description is completely inadequate. It leaves the required parameters, the matching semantics of 'search', and the shape of the returned file list entirely unexplained.

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% for three parameters, two of which (destinationId, search) are required, and the description supplies no semantics at all. The agent cannot tell what 'search' matches against or whether serverId narrows or is required in some contexts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is only the raw route string "GET /backup.listBackupFiles", which restates the tool name rather than stating in prose what the tool does. An agent can guess it lists backup files, but nothing confirms what a "backup file" is or what scope is returned.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no mention of alternatives such as volumeBackups-list or dockerVolume-listVolumeFiles, and no indication of prerequisites like needing a destination first. The agent must infer everything from the name.

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