Skip to main content
Glama
bvisible

MCP SSH Manager

ssh_download

Download files from remote SSH servers to local systems using secure connections. Specify server name, remote file path, and local destination path for file transfers.

Instructions

Download file from remote SSH server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYesServer name
remotePathYesRemote file path
localPathYesLocal destination path

Implementation Reference

  • Registration of 'ssh_download' as part of the essential core SSH operations tool group in the centralized TOOL_GROUPS export.
    core: [
      'ssh_list_servers',
      'ssh_execute',
      'ssh_upload',
      'ssh_download',
      'ssh_sync'
    ],
  • Core file download implementation in SSHManager class. Downloads file from remotePath to localPath using SFTP fastGet, with automatic ~ home directory expansion and error handling. This executes the core logic of the ssh_download tool.
    async getFile(localPath, remotePath) {
      // SFTP doesn't resolve ~ automatically, we need to get the real path
      let resolvedRemotePath = remotePath;
      if (remotePath.includes('~')) {
        try {
          const homeDir = await this.resolveHomePath();
          // Replace ~ with the actual home directory
          // Handle both ~/path and ~ alone
          if (remotePath === '~') {
            resolvedRemotePath = homeDir;
          } else if (remotePath.startsWith('~/')) {
            resolvedRemotePath = homeDir + remotePath.substring(1);
          } else {
            // If ~ is not at the beginning, don't replace it
            resolvedRemotePath = remotePath;
          }
        } catch (err) {
          // If we can't resolve home, throw a more descriptive error
          throw new Error(`Failed to resolve home directory for path: ${remotePath}. ${err.message}`);
        }
      }
    
      const sftp = await this.getSFTP();
      return new Promise((resolve, reject) => {
        sftp.fastGet(resolvedRemotePath, localPath, (err) => {
          if (err) reject(err);
          else resolve();
        });
      });
    }
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 the action but doesn't mention authentication requirements, error handling, file size limits, transfer speed, or whether it overwrites existing local files. For a file transfer operation with zero annotation coverage, this leaves significant behavioral aspects undocumented.

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 communicates the core functionality without any wasted words. It's appropriately sized for a straightforward file transfer operation and gets directly to the point without unnecessary elaboration.

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 file transfer tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens on success/failure, return values, error conditions, or important behavioral aspects like whether it creates directories or handles permissions. The combination of mutation operation (file writing locally) with minimal description creates significant gaps.

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 (server, remotePath, localPath) with basic descriptions. The description adds no additional parameter context beyond what's in the schema - no examples, format requirements, or constraints. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 ('Download') and resource ('file from remote SSH server'), making the purpose immediately understandable. It distinguishes itself from siblings like ssh_upload, ssh_execute, and ssh_sync by focusing specifically on file retrieval. However, it doesn't specify what types of files or protocols are supported, which prevents 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_sync (which might handle bidirectional transfers) and ssh_upload (for opposite direction), there's no indication of when ssh_download is preferred. No prerequisites, constraints, or comparison to other file-related tools 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