Skip to main content
Glama
Sign In
nutstore-mcp

nutstore-mcp

by silverze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

download_file

Download any file from Nutstore cloud to your local machine using remote and local paths. Supports all file formats.

Instructions

从坚果云下载单个文件到本机本地路径。 支持任意格式（文本、图片、PDF、压缩包等）。 local_path 为本机上的目标保存路径，例如 /home/user/docs/report.pdf

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": "download_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
local_pathYes
remote_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It discloses the target as local_path and mentions format support, but does not mention overwrite behavior, directory creation, or other side effects.

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?

Three concise sentences with a clear purpose statement and an example. No unnecessary words.

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?

The description is sufficient for a simple download operation with two parameters and an output schema. It covers purpose and one parameter, but lacks explicit notes on overwriting or directory creation.

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 0%, so the description must compensate. It explains local_path clearly, but remote_path is only implied. This is partial compensation.

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?

The description states a specific action ('download a single file from Nutstore to a local path'), specifies scope ('single file'), and distinguishes from sibling tools like download_dir. It also clarifies format support.

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?

The description clearly indicates this is for single-file downloads (not directories), which differentiates it from download_dir. However, it does not explicitly mention alternatives or when-not-to-use conditions.

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

Deploy Server

Other Tools