Skip to main content
Glama
bvisible

MCP SSH Manager

ssh_backup_list

List available backups on remote servers to manage database and file recovery options, filtering by backup type and specifying directories.

Instructions

List available backups on remote server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYesServer name
typeNoFilter by backup type
backupDirNoBackup directory (default: /var/backups/ssh-manager)

Implementation Reference

  • The 'ssh_backup_list' tool is listed/registered in the backup tool group within the central tool registry.
    backup: [
      'ssh_backup_create',
      'ssh_backup_list',
      'ssh_backup_restore',
      'ssh_backup_schedule'
    ],
  • Generates the shell command to list backups by finding and cat-ing metadata files on the remote server.
    export function buildListBackupsCommand(backupDir = DEFAULT_BACKUP_DIR, type = null) {
      let command = `find "${backupDir}" -name "*.meta.json" -type f`;
    
      if (type) {
        command += ` | grep "${type}_"`;
      }
    
      // Read and parse each metadata file
      command += ' | while read -r file; do cat "$file"; echo "---"; done';
    
      return command;
    }
  • Parses the output from the list backups command into structured backup metadata array, sorted by creation date.
    export function parseBackupsList(output) {
      if (!output || !output.trim()) {
        return [];
      }
    
      const backups = [];
      const metadataBlocks = output.split('---').filter(b => b.trim());
    
      for (const block of metadataBlocks) {
        try {
          const metadata = JSON.parse(block.trim());
          backups.push(metadata);
        } catch (error) {
          logger.warn('Failed to parse backup metadata', { error: error.message, block });
        }
      }
    
      // Sort by created_at descending
      return backups.sort((a, b) => new Date(b.created_at) - new Date(a.created_at));
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it's a listing operation (implied read-only), but doesn't mention authentication requirements, rate limits, output format, pagination, or whether it's safe to run. For a tool that interacts with remote servers, this leaves significant behavioral gaps.

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?

The description is a single, efficient sentence that states exactly what the tool does without any wasted words. It's appropriately sized for a straightforward listing tool and gets directly to the point.

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 tool with no annotations and no output schema that interacts with remote servers, the description is insufficient. It doesn't explain what the output looks like (list format, structure), authentication requirements, or error conditions. Given the complexity of SSH operations and lack of structured metadata, more context is needed.

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?

Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. This meets the baseline for high schema coverage where the description doesn't need to compensate.

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

Purpose4/5

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

The description clearly states the action ('List') and resource ('available backups on remote server'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'ssh_backup_create' or 'ssh_backup_restore' beyond the obvious 'list' vs 'create/restore' distinction, which keeps it from a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'ssh_db_list' and 'ssh_list_servers' that also list resources, there's no indication of when this backup-specific listing tool is preferred over other listing tools or how it relates to backup operations like 'ssh_backup_create'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bvisible/mcp-ssh-manager'

If you have feedback or need assistance with the MCP directory API, please join our Discord server