Skip to main content
Glama

download

Transfer a file or folder from a remote host to your local computer over SSH/SFTP by specifying the host, remote path, and local path.

Instructions

Download a file or folder from a host to this computer.

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": {
      "host": "<host>",
      "remote_path": "<remote_path>",
      "local_path": "<local_path>"
    },
    "name": "download"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
local_pathYesThe path on this computer.
remote_pathYesThe path on the host.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden and says nothing about overwrite semantics for an existing local_path, whether folders are transferred recursively, permission requirements on the remote host, or transfer-size limits. Only the direction of transfer is conveyed, which the parameter names already imply.

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?

A single front-loaded sentence with no wasted wording, and the source-to-destination direction is stated first. Its brevity is efficient, though it edges toward under-specification for a three-required-parameter operation.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description should disclose mutation/overwrite risks, folder-recursion behavior, and any access prerequisites. None of these appear, and the undocumented 'host' parameter leaves the definition materially incomplete for an agent to invoke it safely.

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 67% (local_path and remote_path are documented as 'this computer' vs 'the host'; host is undocumented). The description's phrase 'from a host to this computer' reinforces the host/remote vs local mapping consistently with the schema, but adds no format, syntax, or constraint details for the undocumented host parameter.

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?

"Download a file or folder from a host to this computer" gives a specific verb (download), resource (file or folder), and explicit directionality, which implicitly sets it apart from the sibling 'upload'. It stops short of naming or contrasting the sibling explicitly, so it is clear but not maximally differentiated.

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?

There is no when-to-use guidance, no prerequisites (e.g., whether a session must be open, whether 'request_access' is needed first), and no mention of alternatives such as 'upload' or 'sync_now'. The agent must infer the entire selection context.

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