Skip to main content
Glama

Baidu Delete

baidu_delete

Deletes files from Baidu Netdisk on an fnOS NAS, moving them to the recycle bin. Use it to remove specified netdisk paths via MCP.

Instructions

删除网盘文件(写操作,进入网盘回收站)。

Input Schema

NameRequiredDescriptionDefault
hostNoNAS 主机地址(IP 或域名)
portNoNAS 端口,如 5667(HTTPS)/5666(HTTP)/443
pathsYes网盘内文件路径列表
schemeNo传输协议
profileNo独立 session profile 名称,默认使用 default

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that this is a write operation and that deleted files go to the recycle bin (soft delete), which is important behavioral context. However, it omits authentication requirements, whether permanent deletion is possible, and other operational details.

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 with the core action and key behavior front-loaded. Every word earns its place and there is no unnecessary repetition.

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?

With no annotations and a required paths parameter, the description covers the essential action and soft-delete behavior. Because an output schema exists, return values need not be explained, but the description still lacks usage context and safety-related details such as permissions needed, leaving it adequate but not fully complete.

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 100%, so the schema already documents all five parameters in detail, including paths, host, port, scheme, and profile. The description adds no parameter-level detail beyond the general concept of deleting files, so the baseline 3 applies.

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 states a specific verb (删除) and resource (网盘文件), making it clear this is the Baidu netdisk deletion tool. It does not explicitly distinguish itself from sibling tools like file_delete or baidu_move, but the resource scope is sufficiently specific for an agent to identify it.

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 gives no guidance on when to use this tool versus alternatives such as file_delete or baidu_move. It implies usage through its name and the parenthetical note, but provides no explicit when/when-not/alternatives information.

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