Unified MCP server integrating file operations, system monitoring, download functionality, and PowerShell command execution
Server has 19 tools with basic schemas and descriptions, but significant quality gaps. All tools have descriptions (positive), but most are under 100 chars and lack actionable context. Input schemas are present but minimal, most parameters lack type constraints, enums, or validation guidance. No output schemas documented. Error handling is absent; tools like ps_execute_command (IRREVERSIBLE) lack confirmation patterns or recovery guidance. Naming is verb-noun compliant but generic (e.g., 'get_system_status' vs 'describe_cpu_memory_disk_usage'). No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Composition is reasonable (file ops, download, system, PowerShell separated), but tools like file_edit_file and file_write_file could be unified. Parameter descriptions are minimal, e.g., 'file_path' lacks format/constraint guidance. No pagination support on list_directory. Security: file operations accept arbitrary paths (path traversal risk); PowerShell execution is unrestricted (IRREVERSIBLE operations without confirmation).
顺序批量下载文件
下载单个文件
获取文件基本信息
追加内容到文件
复制文件
创建目录
删除目录
编辑文件内容(替换指定内容)
列出目录内容
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., what does system_get_system_status return? CPU%, memory%, disk%?). Violates pattern:tool and pattern:response-shaper.
Destructive/irreversible operations (file_delete_directory, ps_execute_command, ps_append_command) lack confirmation patterns, dry-run support, or recovery guidance. Agents can cause data loss without safeguards. Violates pattern:confirmation-request.
Parameter descriptions lack actionable constraints. 'file_path' does not specify format, length limits, or path traversal restrictions. 'command' in ps_execute_command lacks examples or allowed command categories. Violates pattern:constrained-input and review:param-validation-rules.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | <=2025-11-25 | v2 |
读取文件内容
写入文件内容
向现有会话追加命令
关闭PowerShell会话
创建新的PowerShell会话
执行PowerShell命令
获取会话的完整输出
获取硬件信息
获取网络状态信息
获取系统实时状态信息
No error handling or recovery guidance. Tools do not document what errors are retryable, user-fixable, or fatal. No guidance on next steps (e.g., 'If file not found, try list_directory first'). Violates pattern:recovery-guide and pattern:error-classification.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). LLMs cannot infer which tools are safe to retry or have side effects. Violates current MCP spec (2026-07-28) tool annotation requirement.