Skip to main content
Glama
pmboxbiz

mcp-ssh-live

by pmboxbiz

ssh_download

Download files from a remote host to a local path via SFTP with atomic writes and configurable size limits to ensure safe, truncated-file-free transfers.

Instructions

Download a file from the remote host to a local path via SFTP. Binary-safe.

Writes to <local_path>.partial first, then atomically replaces the final path on success. A failed or cancelled download never leaves a truncated file where downstream tooling would pick it up.

Size cap: max_bytes (default 100 MiB, hard ceiling 1 GiB). Remote size is checked via sftp.stat BEFORE the transfer starts; files that exceed the cap fail fast. Caps are enforced streaming-side too, so a misreported remote size can't trick us into filling the local disk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
remote_pathYesAbsolute path to the file on the remote host. Tilde expansion is NOT performed (paramiko's SFTP doesn't know about the remote user's ``$HOME``).
local_pathYesWhere to write the file locally. Parent directories are created automatically.
hostNoAlias of the configured host, or a raw address.
max_bytesNoHard cap. Default 100 MiB, clamped to 1 GiB.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description fully carries behavioral transparency. It details atomic write behavior via .partial file, size cap enforcement, pre-check via sftp.stat, and streaming-side protection. This thoroughly discloses failure modes and guarantees.

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?

Description is well-structured with efficient front-loaded main action. Each sentence adds value: download, binary-safe, atomic write, size cap, fail-fast. No unnecessary filler.

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

Completeness5/5

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

Given the presence of an output schema, the description appropriately focuses on behavior and input details. It covers key aspects: download mechanism, atomicity, size constraints, and error prevention. No critical gaps remain.

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 parameters. The description adds minimal extra meaning beyond the schema (e.g., 'Binary-safe' context) but does not significantly enhance parameter understanding beyond what is already in the schema.

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?

Description specifies 'download a file from remote host to local path via SFTP. Binary-safe.' Clearly identifies verb, resource, and distinguishes from siblings like ssh_upload. Provides specific context (SFTP, binary-safe) that enhances understanding.

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?

No explicit guidance on when to use this tool versus alternatives among the 13 sibling tools. The description focuses solely on the tool's mechanics without contextualizing use cases or providing exclusion criteria.

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/pmboxbiz/mcp-ssh-live'

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