Loading ToolBench
AI-powered ArkTS language support with MCP integration for HarmonyOS development. Provides tools for device management, project analysis, app installation/launch, build operations, file transfer, and diagnostics.
20 tools with consistent naming (harmonyos_* prefix) and mostly complete schemas. However, 8 tools (harmonyos_install_app, harmonyos_uninstall_app, harmonyos_launch_app, harmonyos_clear_app_data, harmonyos_tail_hilog, harmonyos_take_screenshot, harmonyos_reboot_device, harmonyos_get_crash_logs) lack visible input schemas in the provided source. Descriptions are present but generic (avg ~60 chars, below 194-char baseline). No output schemas documented. Error handling and recovery guidance absent. Tool composition is sound (single responsibility), but parameter descriptions are minimal. Security: no evidence of secret injection patterns or permission gates.
Trigger a HarmonyOS build by running hvigorw in the project root. Returns stdout/stderr output. May take several minutes.
Check if build outputs exist and list them
Clear application data on a device
Get detailed information about an installed application
Get memory usage of a running app by bundle name using hidumper. The app must be running on the device.
List crash logs in /data/log/faultlog/ on the device, optionally filtered by bundle name. Set fetchLatest=true to also pull the most recent log file to the host.
Get detailed information about a specific device
8 tools lack visible input schemas (harmonyos_install_app, harmonyos_uninstall_app, harmonyos_launch_app, harmonyos_clear_app_data, harmonyos_tail_hilog, harmonyos_take_screenshot, harmonyos_reboot_device). Cannot verify parameter types or constraints.
No output schemas documented for any tool. LLMs cannot infer response structure, forcing them to parse unstructured text. Baseline: 100% of A+ tools document return types.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
Get HarmonyOS project information (bundleName, version, modules)
Install an application on a device
Launch an application on a device
Parse oh-package.json5 in the project root and each module to list all npm/ohpm dependencies and devDependencies.
List all connected HarmonyOS devices
List all installed applications on a device
List all modules in a HarmonyOS project with their types
Pull a file from a connected HarmonyOS device to the host machine. Wraps `hdc file recv`. Defaults localPath to OS temp dir.
Push a local file to a path on a connected HarmonyOS device. Wraps `hdc file send`.
Reboot a connected HarmonyOS device
Stream device logs in real-time
Take a screenshot from a device
Uninstall an application from a device
Descriptions are generic and brief (avg ~60 chars, baseline 194 chars). Examples: 'List all connected HarmonyOS devices' (40 chars), 'Get detailed information about a specific device' (48 chars). Missing WHEN to use, prerequisites, and actionable context for LLM selection.
No error handling or recovery guidance. Tools like harmonyos_build (long-running, may fail) and harmonyos_reboot_device (irreversible) lack error classification, retry hints, or confirmation patterns.
Destructive/irreversible tools (harmonyos_uninstall_app, harmonyos_clear_app_data, harmonyos_reboot_device) lack confirmation or dry-run patterns. Agents can trigger destructive actions without safeguards.