Skip to main content
Glama
Sign In
nutstore-mcp

nutstore-mcp

by silverze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_file

Delete a file or directory in Nutstore cloud storage. Caution: this action is permanent and cannot be undone.

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": {
      "path": "<path>"
    },
    "name": "delete_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

There are no annotations, so the description must disclose behavior. It only mentions deletion and provides a caution, but it does not state whether deletion is permanent, if it supports recursive deletion for directories, whether files go to a recycle bin, or what permissions are required. This is a significant gap for a destructive tool.

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 action and the target, with a useful caution. Every word earns its place, and the structure is clean and front-loaded.

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 destructive operation with no annotations and minimal schema information, the description is insufficient. It lacks essential details about deletion semantics, path handling, and consequences, leaving the agent without enough context to invoke the tool safely and correctly.

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

Parameters2/5

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

The schema has a single 'path' parameter with no description (0% coverage). The tool description adds that the path refers to a file or directory in Nutstore, but does not clarify path format, absolute vs. relative paths, or any constraints. Given the low schema coverage, the description fails to compensate adequately.

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 verb 'delete' and the target resource 'files or directories in Nutstore', making the tool's purpose unmistakable. It distinguishes itself from siblings like list, search, and read, and the caution flag reinforces that this is a destructive operation.

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?

No guidance is given on when to use this tool versus alternatives such as batch_delete or move_file. The caution 'use with caution' is a general warning but does not provide specific decision-making context or exclusion criteria.

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