Skip to main content
Glama
synology-mcp
by r03eRt

Download to this computer

download_file
Read-only

Download files or folders from a Synology NAS to a local destination, combining multiple selected paths or a folder into a single ZIP archive.

Instructions

Download files/folders from the NAS to a local path on this computer. Several paths (or a folder) are downloaded as a single ZIP.

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": {
      "paths": "<paths>",
      "local_path": "<local_path>"
    },
    "name": "download_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYes
overwriteNoOverwrite the local file if it exists (default false)
local_pathYesLocal destination: an existing folder, or a full file path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is largely supplied structurally; the description adds the notable behavioral facts that multiple paths are bundled into a single ZIP and that the destination can be a folder or a full file path. There is mild tension with readOnlyHint=true because the operation writes to local disk and can overwrite existing files (documented in the schema, not the description), so an agent could underestimate the local side effect. The description also says nothing about how missing remote paths or existing destinations are handled beyond the overwrite flag.

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?

Two sentences with no filler, and the transfer direction plus location are front-loaded ahead of the ZIP bundling detail. Every clause carries information an agent needs.

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 three-parameter tool with no output schema, the definition covers what the tool does but omits what the agent gets back — nothing about the resulting local file name, the ZIP's name or location, or behavior when the download fails. Given there is no output schema to describe return values, the description should have carried at least the identity of the produced artifact.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, with overwrite and local_path already self-documented, so the schema carries most of the load. The description earns credit for clarifying the array semantics of 'paths' — several paths or a single folder collapse into one ZIP — which is a meaning the schema's array type does not convey. The remote path prefix constraint is left entirely to the schema.

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 uses a specific verb and resource ('Download files/folders from the NAS') and states the direction of transfer ('to a local path on this computer'), which an agent can act on immediately. It stops short of naming a sibling, so nothing distinguishes it from read_file or downloads_get, but the purpose itself is unambiguous.

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?

Usage is only implied: the mention of a 'local path on this computer' tells the agent this is for copying content off the NAS rather than inspecting it, which rules out read_file by inference. There is no explicit when-to-use or when-not-to-use statement, and no guidance on choosing this over the downloads_* siblings.

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