Skip to main content
Glama

ssh_download

DestructiveIdempotent

Copy a file or directory from a remote server to your local machine, using sha256 checks to ensure data integrity, including root-owned files via temporary staging.

Instructions

Copies a file or directory from a server to this machine. Data lands under a temporary name and takes its place in one rename, and every file is checked by sha256 on both sides; a machine without sha256 answers 'unavailable', which means delivered, not broken. A root-owned copy stages in /tmp on the server, so it needs room there. To read a text file rather than keep it, ssh_file_read skips the disk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sudoNoFor /root and the like. A root copy stages in /tmp, is fetched and removed — the machine needs room. Default: false
verifyNosha256 on both sides, per file. "unavailable" = no sha256 on the machine = delivered, not broken. Default: true
profileYesMachine name.
timeoutNoMilliseconds. No ceiling by default — a transfer runs as long as it takes.
recursiveNoOnly to force it — a directory is recognised on its own.
local_pathYesWhere it lands on this machine.
remote_pathYesWhat to fetch from the server.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesNo
legendNoWhat the words in this answer mean. A key names the field before the value — "state=limited", "jobs[].state=lost" — and only the values this answer actually used are listed.
Behavior4/5

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

Beyond the idempotent and destructive hints, the description details the use of temporary names, sha256 checks, handling of root-owned files via /tmp staging, and the 'unavailable' response when sha256 is missing. These are concrete behavioral details not present in annotations.

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

Conciseness2/5

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

The description is verbose and uses metaphorical language ('Data lands under a temporary name and takes its place in one rename') that obscures the meaning. It lacks straightforward structure and could be significantly condensed for clarity.

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 description covers the main functional aspects: transfer, verification, root handling, and alternative usage. However, it does not clearly explain when to prefer this tool over others (beyond text files) or address potential pitfalls. It is adequate but not comprehensive.

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 includes descriptions for all parameters, and the tool description does not add further clarification or nuance. Since schema coverage is 100%, the baseline of 3 is appropriate; the description offers no extra meaning.

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 core purpose: copying a file or directory from a server to this machine. It also mentions the sha256 verification and the alternative for text files. However, the phrasing is convoluted with metaphors, making it less crisp than an ideal purpose statement.

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?

It explicitly contrasts with ssh_file_read, indicating when to use this tool for downloads versus reading a text file. It does not explicitly say 'use this when you need to transfer files', but the verb 'copies' makes that implicit. The alternative is clearly stated.

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/hypnosis/ssh-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server