Loading ToolBench
Exposes a device's filesystem, terminal, and Git operations as MCP tools for remote Hermes Agent access. Enables multi-device collaboration with security features including path whitelisting and HMAC authentication.
Server provides 11 tools with basic schemas and descriptions in Chinese. All tools have input schemas with type definitions and parameter descriptions, meeting minimum requirements. However, descriptions are minimal (10-50 chars), lack actionable context for LLM selection, and omit critical details like prerequisites, return types, and error guidance. No output schemas documented. Tool names follow verb_noun pattern but lack clarity on distinctions (e.g., git_* tools could benefit from more specific naming). Security features (whitelist, HMAC) are implemented server-side but not reflected in tool documentation. Error handling returns plain text without recovery guidance. Composition is reasonable, each tool has single responsibility, but chaining information is missing from responses.
Git add + commit。
查看 Git diff。
查看 Git 提交历史。
执行 git pull。
执行 git push。
查看 Git 仓库状态。
列出目录内容。返回文件名、大小、类型。
读取文件内容，带行号。
Descriptions are too brief (10-30 chars) and lack LLM-optimized context. E.g., git_pull is '执行 git pull' (8 chars), does not explain when to use it vs git_fetch, what it returns, or prerequisites. Baseline: 194 chars average for A+ tools.
No output schemas documented. Tools return plain text (JSON for list_files, unstructured strings for git_* and run_command). LLMs cannot plan downstream calls or extract structured data. Baseline: 100% of A+ tools document return types.
Error handling returns plain text without recovery guidance. E.g., 'PermissionError: path not in whitelist' gives no hint to retry with a different path or call a discovery tool. Baseline: errors must guide next steps.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | 2026-07-28+ | v2 |
在这台设备上执行终端命令。
查看这台设备的系统信息。
写入文件（完整覆盖）。
Destructive operations (write_file, git_pull, git_push, git_commit, run_command) lack confirmation or dry-run support. Agents can accidentally overwrite files or push broken commits without safeguards.
Git tools (git_pull, git_push, git_commit) lack clarity on prerequisites (repo must exist, credentials configured). Descriptions do not explain when to call git_status first or what 'staged' means in git_diff.