MCP server for uploading and downloading files/folders to/from Baidu Pan (百度网盘)
All 4 tools have minimal descriptions (Chinese text, 10-16 chars) and lack proper parameter documentation. Input schemas are present but parameters lack descriptions in the schema itself. No output schemas documented. Tools perform file I/O operations (WRITE risk) with no error handling guidance, validation, or recovery patterns. No tool annotations (destructiveHint, idempotentHint). Descriptions fall far below the 10-1024 char baseline and provide no context for LLM selection or prerequisites.
下载文件到本地
下载文件夹到本地
上传文件到百度网盘
上传文件夹到百度网盘
All tool descriptions are under 20 characters (Chinese text only: '上传文件到百度网盘', '下载文件到本地', etc.). Descriptions must be 10-1024 chars and explain WHAT, WHEN, and any prerequisites.
Input parameters lack descriptions in schema. 'src_file', 'src_path', 'target_file', 'target_path' have no schema-level descriptions. LLMs cannot infer parameter meaning from names alone (e.g., is 'src_file' a local path or remote path?).
No output schemas documented. Tools return plain strings ('上传成功', '下载成功'). LLMs cannot plan downstream calls or extract structured data. Per pattern:tool, output schema must be documented.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 35 | 2026-07-28+ | v2 |
No error handling or recovery guidance. Tools perform destructive file I/O (WRITE risk) with no try-catch, validation, or error messages. If upload fails, LLM receives no actionable error. Per pattern:recovery-guide, errors must tell LLM what to do next.
No tool annotations (destructiveHint, idempotentHint). All tools perform file I/O but lack metadata indicating they are destructive/non-idempotent. LLMs cannot reason about retry safety or side effects.