Skip to main content
Glama
Sign In
SSH MCP Server

SSH MCP Server

by tufantunc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sftp-download

Read-only

Safely fetch a file from a remote Linux or Windows host over SSH. Use to retrieve files securely by specifying the remote path, solving the need to pull data without manual transfer.

Instructions

Download a file from the remote server via SFTP.

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": {
      "remotePath": "<remotePath>"
    },
    "name": "sftp-download"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoProfile name
remotePathYesRemote file path. No leading or trailing whitespace, and no control, bidirectional or zero-width characters: the approval prompt and the audit record quote this path back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.11.0
    • changedInput schema / properties / remotePath / description
      Previous value: -"Remote file path to download"New value: +"Remote file path. No leading or trailing whitespace, and no control, bidirectional or zero-width characters: the approval prompt and the audit record quote this path back."
  2. First observedv2.5.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds minimal behavioral context beyond that, such as the fact that it downloads from a remote server. It does not disclose details like whether a session must be open, how the file is transferred, or what happens on failure, but the annotation covers the safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that front-loads the action and resource. It is efficient and easy to parse, though it could add a bit more context without becoming verbose.

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

Completeness3/5

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

For a simple download tool with full schema coverage and a readOnlyHint annotation, the description is mostly adequate. However, it lacks guidance on prerequisites (e.g., an open session) and does not clarify the relationship to sibling tools like sftp-download-file, which could lead to incorrect selection in a larger toolset.

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 both parameters. The description adds no additional meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb ('Download') and resource ('a file from the remote server via SFTP'), which clearly identifies the tool's core action. It does not explicitly distinguish itself from sibling tools like sftp-download-file, but the action and resource are clear enough for basic selection.

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

Usage Guidelines3/5

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

The description implies usage context (downloading via SFTP) but provides no explicit guidance on when to choose this tool over alternatives such as sftp-download-file or sftp-list. There is no mention of prerequisites like an open session or connection, which would help an agent decide when to invoke it.

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

Deploy Server

Other Tools