网易春风 · 心跳元力 MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_devicesC | 扫描并列出附近已知的心跳元力 BLE 设备。 |
| connect_deviceC | 连接指定的心跳元力 BLE 设备并发现 GATT 能力。 |
| get_device_statusB | 读取 MCP 自己持有的设备连接、profile 和 GATT 状态。 |
| set_vibrationC | 设置 DK-META2 振动强度；非零值必须 confirm=true。 |
| set_linearB | 设置 DK-META2 伸缩强度；非零值必须 confirm=true。 |
| set_rotaryB | 设置 DK-META2 旋转强度；非零值必须 confirm=true。 |
| stop_deviceA | 将当前设备所有已支持输出归零；可重复调用。 |
| disconnect_deviceA | 停止心跳并断开 MCP 持有的 BLE 连接。 |
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 8 tools
Each tool has a distinct role across the BLE lifecycle: discovery, connection, status, modality-specific output control, stopping outputs, and disconnection. The three set_* tools are clearly separated by vibration, linear, and rotary outputs, while stop_device and disconnect_device are distinguishable by scope.
All tool names use consistent snake_case with verb_noun or verb_noun_noun structure. list_devices, connect_device, get_device_status, set_vibration, set_linear, set_rotary, stop_device, and disconnect_device follow the same predictable convention.
Eight tools are well-scoped for a BLE device control server. The set covers discovery, connection management, status inspection, three independent output modes, emergency stop, and disconnect without unnecessary bloat.
The surface covers the core device control lifecycle and operation modes well. Minor gaps remain around reading current output intensities or device telemetry such as battery/firmware, but agents can complete the main workflows.