Skip to main content
Glama
bvisible

MCP SSH Manager

ssh_backup_create

Create compressed database or file backups on a remote server over SSH, with automatic retention cleanup.

Instructions

Creates a database or file backup on the remote server over SSH, writing a compressed archive plus a JSON metadata file into backupDir. Supports mysql, postgresql, mongodb, and files (full is not yet implemented and errors). Database types require database; files requires paths. After writing it prunes backups older than retention days (default 7); compress defaults to true. Runs pre-backup and post-backup hooks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYesServer name
typeYesBackup type: mysql, postgresql, mongodb, files, or full
nameYesBackup name (e.g., production, app-data)
databaseNoDatabase name (required for db types)
dbUserNoDatabase user
dbPasswordNoDatabase password
dbHostNoDatabase host (default: localhost)
dbPortNoDatabase port
pathsNoPaths to backup (for files type)
excludeNoPatterns to exclude from backup
backupDirNoBackup directory (default: /var/backups/ssh-manager)
retentionNoRetention period in days (default: 7)
compressNoCompress backup (default: true)
Behavior4/5

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

With no annotations, the description discloses key behaviors: backup types, conditional parameter requirements, pruning by retention, default compress=true, and pre/post hooks. It does not mention potential side effects like overwrite behavior or failure modes, but coverage is good.

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 well-structured paragraph without fluff. It is front-loaded with the main action and efficiently covers all key points: what it does, types, constraints, defaults, and additional behaviors (hooks, pruning).

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

Completeness4/5

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

Given the complexity (13 params, 4 types, conditional requirements, defaults, pruning, hooks), the description is mostly complete. It mentions output (compressed archive + JSON metadata) but does not describe the return value or success/failure indicators. However, for a creation tool, this is sufficient.

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

Parameters5/5

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

Schema coverage is 100%, so baseline is 3. The description adds significant value beyond the schema: clarifies defaults (backupDir, retention, compress), conditional requirements (database for db types, paths for files), and explicitly warns that 'full' errors. This is highly informative.

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 action 'Creates a database or file backup' with specific resources (remote server, compressed archive, metadata file). It distinguishes from sibling tools like ssh_backup_list, ssh_backup_restore, and ssh_backup_schedule.

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

Usage Guidelines4/5

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

The description provides clear context on when to use the tool (creating backups) and notes that 'full is not yet implemented and errors'. It does not explicitly state when not to use it or mention alternatives, but sibling names suffice for differentiation.

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