Skip to main content
Glama

ugreen_download_file

Download a file from the NAS to a specified local absolute path, refusing to overwrite existing files by default so local processing can continue safely.

Instructions

把一个 NAS 文件下载到用户指定的本机绝对路径。默认拒绝覆盖已有文件。下载内容可用 Codex 的本地文件工具继续处理。

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

Input Schema

NameRequiredDescriptionDefault
local_pathYes
remote_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare a non-readOnly, openWorld, non-idempotent, non-destructive write. The description adds one genuinely useful behavioral rule not present in the annotations: existing files are refused by default. However, the word 'default' implies an overwrite option that the schema does not expose, and nothing is said about failure modes, partial files, or permissions for an openWorld write.

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?

Three short sentences with the core action front-loaded, followed by the overwrite rule and a chaining hint. Nothing is padded, though the final sentence about Codex file tools is meta-guidance rather than essential calling information.

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

Completeness4/5

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

No output schema exists, yet the description does not state what is returned (local path, file size, status). For a simple two-parameter download that gap is small, and purpose, path semantics, overwrite policy, and a follow-on step are all covered, making the definition largely sufficient.

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?

With 0% schema description coverage on two required parameters, the description carries the load and does add value: it specifies that local_path must be an absolute path and that remote_path refers to a NAS-side file. It does not clarify path formats, separators, or what happens if the remote path is a directory, so the compensation is partial.

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?

Names a specific verb and resource (download a NAS file to a local absolute path), which implicitly separates it from NAS-to-NAS siblings such as ugreen_copy_file or ugreen_move_file. It does not name an alternative explicitly, so it stops short of full sibling differentiation.

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?

The description provides only implied guidance: it states a destination requirement and that the resulting file can be passed to Codex local file tools, which hints at a follow-on workflow. It does not say when to prefer this over ugreen_copy_file, nor does it mention prerequisites such as NAS connectivity or authentication.

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