List existing backup archives stored in the configured backup directory, optionally on a remote server. Verify available backups and identify the right archive for restore.
List existing backup archives in the configured backup directory
| Name | Required | Description | Default |
|---|---|---|---|
| server | No | Remote server name from config (optional, runs locally if omitted) |
Changes observed during successful MCP inspections.
v0.18.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description only implies a safe read operation but does not disclose error handling, permissions, or directory existence behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence with no unnecessary words, efficiently conveying the tool's core function.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a listing tool with no output schema, the description is adequate but lacks details on whether the list includes metadata like dates or sizes; sibling differentiation is not addressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (single parameter already described), and the description adds no additional meaning beyond the schema's description of the 'server' parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists existing backup archives, with a specific verb and resource, distinguishing it from sibling backup tools that create, drill, or restore backups.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like backup_drill or backup_restore; the description lacks context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.