Skip to main content
Glama
Sign In
claude-ssh-mcp

claude-ssh-mcp

by MaraBank
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

ssh_download

Download files from remote servers to your local machine using SFTP. Specify the session, remote path, and local destination.

Instructions

Download a file from a remote server to the local machine 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": {
      "sessionName": "<sessionName>",
      "remotePath": "<remotePath>",
      "localPath": "<localPath>"
    },
    "name": "ssh_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionNameYesSession to download from
remotePathYesAbsolute path on the remote server
localPathYesAbsolute local destination path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic operation. It does not disclose whether the local file is overwritten, if directories are created, authentication requirements, or potential side effects. This is a significant gap.

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?

Single sentence of 10 words, no wasted text. Front-loaded with the core verb and resource, making it immediately scannable.

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?

The tool is simple, but the description lacks details on behavior (e.g., overwrite policy, return value, error handling). Given no output schema, the description should provide more context to ensure safe usage.

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 has 100% coverage for all three required parameters. The description adds no extra meaning beyond the schema descriptions, which are already clear. Baseline 3 is appropriate.

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 explicitly states the action (Download), resource (a file), and method (via SFTP). It clearly distinguishes from sibling tools like ssh_upload (opposite direction) and ssh_transfer (potentially bidirectional).

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?

No guidance is provided on when to use this tool versus alternatives, such as ssh_transfer or when a session must be established first via ssh_connect. The agent is left to infer prerequisites and context.

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