mcp-ssh

by zhouxiangjing

Overview Schema Source Related Servers Discussions Admin

Python

Local

download_file

Retrieve a file from a remote server and save it to a local path via SFTP, using the remote and local paths.

Instructions

Download a file from the remote server to local via SFTP.

Args: remote_path: Absolute file path on the remote server. local_path: Destination absolute local path (on the machine running this MCP server). host_name: Named host from SSH_HOSTS config; uses default host if omitted.

Returns: Success message with transferred file size, or error details.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "remote_path": "<remote_path>",
      "local_path": "<local_path>"
    },
    "name": "download_file"
  }
}

Input Schema

Name	Required	Description	Default
`host_name`	No
`local_path`	Yes
`remote_path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5Aug 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations, the description carries the full transparency burden. It mentions the SFTP protocol and return format, but does not disclose potential overwrite behavior, directory creation, authentication prerequisites, or other side effects. This leaves some ambiguity for a file operation.

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 well-structured with Args and Returns sections, front-loaded with the core purpose. Every sentence provides necessary information without redundancy or padding.

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?

The description covers the tool's purpose, parameters, and return values, making it complete for a straightforward download operation. It does not cover edge cases like overwrite policy or error handling specifics, but these are not critical given the tool's simplicity and the presence of an output schema.

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?

The description provides thorough explanations for all three parameters, adding meaning beyond the schema. It clarifies that paths are absolute and that host_name selects from SSH_HOSTS config with a default fallback, which significantly aids correct usage.

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 tool downloads a file from remote to local via SFTP, using specific verbs and resources. It is distinct from siblings like upload_file, which performs the reverse operation.

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 about the host_name parameter and default behavior, but does not explicitly mention when to use this tool versus alternatives like upload_file. However, the purpose is so specific that usage is implied.

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