cardeck
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Bridge server port. Defaults to 8787. | 8787 |
| PUBLIC_BASE | No | Public base URL used for APK download links. | |
| BRIDGE_PAIRING | No | Fixed pairing code. If not set, a random pairing code is generated. | |
| BRIDGE_AUTO_PROMPT | No | Controls automatic stability/reproduction prompts on the phone. Set to 0 to disable. | |
| BRIDGE_STABLE_SECONDS | No | Number of quiet seconds required before prompting that the connection is stable. Defaults to 10. | 10 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bridge_statusC | 桥状态:配对码与在线设备列表 |
| logs_tailC | 取设备最近 N 行日志 |
| logs_fetchB | 取设备 sinceSeq 之后的日志(增量拉取;读磁盘落盘文件,含全部例行行、跨进程世代) |
| logs_fileB | 拉设备文件日志(main_debug.log 尾部,含 RAW 协议转储的完整事实源;gzip 传输,落盘到 logs/ 供直接 grep) |
| cmdC | 向设备下发白名单命令(start_connection/stop_connection/get_state/ping) |
| notifyC | 在设备悬浮窗上显示提示文字 |
| prompt_reproduceB | 在设备悬浮窗提示用户开始复现问题(稳定判定之外的手动触发;text 可自定义引导语) |
| watch_stabilityC | 查看/配置会话稳定判定(auto 开关、静默窗口秒数;稳定后自动提示用户复现) |
| offer_apkB | 向设备推送新 APK(复制到 public/ 并下发安装提示;filePath 为本地 APK 绝对路径) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Three log tools (logs_tail, logs_fetch, logs_file) and two user-prompt tools (notify, prompt_reproduce) overlap enough that an agent may hesitate despite the descriptions differentiating them. Other tools target clearly distinct actions such as status, APK push, commands, and stability configuration.
Names are mostly snake_case but mix noun-first patterns (logs_tail, bridge_status) with verb-first patterns (offer_apk, watch_stability) and a bare abbreviation (cmd). The set remains readable, but the naming convention is not predictable throughout.
Nine tools is well within the ideal range for a device bridge/debugging server. Each tool maps to a distinct operational area, even if the three logging tools could be consolidated in a stricter design.
The surface covers device status, log retrieval, APK push, whitelisted commands, user notifications, reproduction prompting, and stability configuration. Minor gaps exist around APK install verification, device selection, and log clearing, but core debugging workflows are covered.