MCP server that exposes Android Agent core functionality for automated Android device control and task execution. Supports device management, task planning, execution monitoring, and error diagnostics.
Server has 17 tools with significant quality gaps. Most tools lack proper English descriptions (many in Chinese), parameter descriptions are minimal or absent, and schemas are incomplete. Tool naming is inconsistent (mix of snake_case and camelCase). No output schemas documented. Error handling is minimal. Only 5 tools have descriptions >20 chars in English. This is a D-grade implementation with major structural issues.
列出设备上所有已安装的应用包名 (pm list packages) , 注意包名称无法使用 am start 启动!
发送系统广播 (am broadcast)
立即终止指定 Android 设备上正在运行的任务。用于在观察到 Agent 行为偏离预期或需要紧急停止时使用。
读取 Android Agent 最近记录的 50 条错误日志。用于排查系统异常、任务失败原因或调试内部错误。
获取所有已连接的安卓设备(包括物理真机和红机虚拟机)的列表。展示设备型号、状态以及当前正在执行的任务进度。
启动一个新的 Android Agent 任务。它会自动寻找并锁定一台空闲设备(物理机或虚拟机),根据你的需求进行规划并执行自动化操作。
查询指定 Android 设备上当前任务的详细进度。包括任务状态(运行中/成功/失败)、已完成步骤的简要日志以及最终结论。如果有进行中的活动可以询问用户是否可以终止活动开始新活动。
Descriptions in Chinese language prevent LLM understanding. Tools like butt_android_run, butt_android_status, butt_android_abort, butt_android_errorLog, butt_android_listDevices have Chinese-only descriptions. LLMs trained primarily on English will fail to select these tools correctly.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields. Tools return generic {status, message, data} but structure of 'data' is undocumented.
Inconsistent naming convention: mix of snake_case (butt_android_run, butt_android_status) and camelCase (forceStop, getCurrentApp, disableUser). LLMs struggle with inconsistent naming patterns.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 43 | <=2025-11-25 | v2 |
清空应用数据和缓存 (pm clear)
禁用指定应用,禁用后从桌面消失并停止运行 (pm disable-user)
强制停止指定应用 (am force-stop)
获取当前前台运行的应用包名和 Activity 名
查看当前所有后台任务栈 (am stack list)
安装 APK(需先将 APK push 到手机)(pm install)
输出拆解后的任务计划列表,输出规范:{allPlan:string[]}
启动指定应用或网页。注意:app启动路径应该从 [launcherAppList] 获取。
任务完成。【当你已经完成任务 或 者确定本次操作后可完成任务可以同步调用此工具】
卸载应用 (pm uninstall)
Parameter descriptions missing or minimal. Tools like getStackList, getCurrentApp, getStackList have empty parameter objects with no descriptions. Even tools with parameters (start, install) lack detailed format/constraint documentation.
No error handling guidance. Tools return generic error messages like 'Invalid input' without actionable recovery steps. LLMs cannot self-correct or determine if errors are retryable.