Skip to main content
Glama
bvisible

MCP SSH Manager

ssh_sync

Synchronize files between local and remote systems using rsync for automated deployment and backup workflows.

Instructions

Synchronize files/folders between local and remote via rsync

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYesServer name from configuration
sourceYesSource path (use "local:" or "remote:" prefix)
destinationYesDestination path (use "local:" or "remote:" prefix)
excludeNoPatterns to exclude from sync
dryRunNoPerform dry run without actual changes
deleteNoDelete files in destination not in source
compressNoCompress during transfer
verboseNoShow detailed progress
checksumNoUse checksum instead of timestamp for comparison
timeoutNoTimeout in milliseconds (default: 30000)

Implementation Reference

  • The tool 'ssh_sync' is listed in the 'core' group of TOOL_GROUPS. This registry is used centrally for conditional MCP tool registration based on user configuration from tool-config-manager.js.
    core: [
      'ssh_list_servers',
      'ssh_execute',
      'ssh_upload',
      'ssh_download',
      'ssh_sync'
    ],
  • Test file expects 'ssh_sync' as part of core tools, validating the tool registry.
    const expectedCore = ['ssh_list_servers', 'ssh_execute', 'ssh_upload', 'ssh_download', 'ssh_sync'];
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'synchronize' which implies a potentially destructive operation (e.g., overwriting files), but doesn't clarify risks, permissions needed, or what happens on errors. For a tool with 10 parameters and no safety annotations, 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 that directly states the tool's function without unnecessary words. It's front-loaded with the core purpose, making it easy to parse quickly.

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?

Given the complexity (10 parameters, no output schema, and no annotations), the description is inadequate. It doesn't explain the tool's behavior, output format, error handling, or how it differs from similar tools, leaving significant gaps for an AI agent to understand its proper use.

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?

The schema description coverage is 100%, meaning all parameters are documented in the input schema. The description adds no additional parameter information beyond implying rsync-like behavior, so it meets the baseline of 3 without compensating for any gaps.

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 ('synchronize') and resource ('files/folders between local and remote via rsync'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like ssh_upload or ssh_download, which also handle file transfers, so it doesn't reach the highest 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 like ssh_upload or ssh_download, nor does it mention any prerequisites or context for usage. It's a standalone statement without comparative or contextual information.

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