Skip to main content
Glama
Sign In
nutstore-mcp

nutstore-mcp

by silverze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_file

Move or rename files and directories in Nutstore cloud storage. Specify source and destination paths to reorganize your files.

Instructions

移动或重命名坚果云中的文件/目录

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": {
      "src_path": "<src_path>",
      "dst_path": "<dst_path>"
    },
    "name": "move_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
dst_pathYes
src_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.7/5.0
Behavior1/5

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

With no annotations, the description must disclose behavioral traits but only states the operation. It omits critical details such as side effects (source removal), overwrite behavior, path handling, permissions, or error conditions. The description adds no value beyond the basic definition.

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?

The description is a single concise sentence that immediately communicates the core function. There is no fluff or redundant wording, making it highly efficient for an agent to parse.

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?

Even with an output schema present, the description omits essential context for a mutation tool: destination-collision behavior, atomicity, error cases, and whether metadata is preserved. The lack of annotations and minimal description leaves significant gaps for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description adds no explanation of src_path and dst_path semantics. It doesn't clarify path formats, whether paths are relative or absolute, or any operational behaviors tied to each parameter, leaving the agent to guess from parameter names alone.

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 clearly states the tool moves or renames files/directories in Nutstore, using specific verbs and a resource type. This distinguishes it from sibling tools like copy_file and delete_file, making its purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives like copy_file or delete_file. There are no usage scenarios, prerequisites, or exclusions, leaving the agent to infer usage solely from the tool name and operation type.

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