Skip to main content
Glama
bvisible

MCP SSH Manager

ssh_backup_schedule

Schedule automated backups for databases and files on SSH servers using cron. Configure retention periods and specify backup types including MySQL, PostgreSQL, MongoDB, and file systems.

Instructions

Schedule automatic backups using cron

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYesServer name
scheduleYesCron schedule (e.g., "0 2 * * *" for daily at 2 AM)
typeYesBackup type
nameYesBackup name
databaseNoDatabase name (for db types)
pathsNoPaths to backup (for files type)
retentionNoRetention period in days (default: 7)

Implementation Reference

  • Registration of 'ssh_backup_schedule' tool in the backup group of TOOL_GROUPS
    // Backup group (4 tools) - Backup and restore operations
    backup: [
      'ssh_backup_create',
      'ssh_backup_list',
      'ssh_backup_restore',
      'ssh_backup_schedule'
    ],
  • Core helper function to build the shell command for scheduling a backup job using crontab on the remote server
     * Build cron schedule command
     */
    export function buildCronScheduleCommand(schedule, backupCommand, cronComment) {
      // Add cron job with comment
      const cronLine = `${schedule} ${backupCommand} # ${cronComment}`;
      return `(crontab -l 2>/dev/null; echo '${cronLine}') | crontab -`;
    }
  • Helper function to parse the output of crontab -l and extract scheduled backup jobs
    /**
     * Parse cron list output
     */
    export function parseCronJobs(output) {
      if (!output || !output.trim()) {
        return [];
      }
    
      const jobs = [];
      const lines = output.split('\n');
    
      for (const line of lines) {
        if (line.trim() && !line.startsWith('#') && line.includes('ssh-manager-backup')) {
          const parts = line.split('#');
          const schedule = parts[0].trim();
          const comment = parts[1] ? parts[1].trim() : '';
    
          jobs.push({
            schedule,
            comment,
            command: schedule.split(/\s+/).slice(5).join(' ')
          });
        }
      }
    
      return jobs;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'automatic backups' and 'cron', implying a recurring scheduled operation, but lacks critical behavioral details: whether this creates persistent cron jobs, requires SSH access or specific permissions, what happens on schedule conflicts, error handling, or confirmation of setup. For a mutation tool with zero annotation coverage, this is insufficient.

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 with zero waste. It's front-loaded with the core purpose and uses minimal words to convey the essential action and mechanism. Every word earns its place without redundancy.

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 complex mutation tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It lacks behavioral context (permissions, persistence, errors), usage guidance relative to siblings, and any indication of what the tool returns (e.g., confirmation, job ID). The high parameter count and mutation nature demand more comprehensive description.

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 fully documents all 7 parameters with clear descriptions and enums. The description adds no parameter-specific information beyond what's in the schema (e.g., no examples for 'name' or 'retention', no clarification on 'type' interactions). Baseline 3 is appropriate when schema does the heavy lifting.

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 ('schedule automatic backups') and mechanism ('using cron'), which is specific and actionable. It distinguishes from siblings like ssh_backup_create (one-time) and ssh_backup_list (viewing), though not explicitly named. However, it doesn't fully differentiate from potential scheduling alternatives in the sibling list.

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_backup_create (one-time backup) and ssh_backup_restore (recovery), there's no indication that this is for recurring backups versus one-time operations. No prerequisites, exclusions, or contextual triggers are mentioned.

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