MCP Reminder
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_ENDPOINT | Yes | The WebSocket endpoint URL for connecting to the Xiaozhi MCP service, including the access token (e.g., wss://api.xiaozhi.me/mcp/?token=YOUR_TOKEN). |
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 |
|---|---|
| add_alarmB | 添加闹钟 Args: time: 闹钟时间,支持自然语言如"下午2点30分"、"明天上午10点"或精确时间"2025-09-02 14:30" description: 闹钟描述(可选) Returns: 包含闹钟ID和确认信息的字典 |
| get_pending_alarmsB | 获取所有到期的闹钟 小智会定期调用此接口检查是否有需要提醒的闹钟 Returns: 包含到期闹钟列表的字典 |
| dismiss_alarmC | 关闭/删除闹钟 Args: alarm_id: 闹钟ID Returns: 操作结果 |
| add_todoB | 添加待办事项 Args: title: 待办事项标题 remind_time: 提醒时间(可选),支持自然语言如"明天下午3点" description: 待办事项描述(可选) Returns: 包含待办ID和确认信息的字典 |
| get_pending_todosC | 获取所有到期且未完成的待办事项 小智会定期调用此接口检查是否有需要提醒的待办 Returns: 包含到期待办列表的字典 |
| complete_todoC | 完成待办事项 通过标题关键词匹配待办事项并标记为已完成 Args: title: 待办事项标题或关键词 Returns: 操作结果 |
| list_todosB | 列出待办事项 Args: status: 筛选状态,可选值: "pending"(未完成)、"completed"(已完成)、"all"(全部),默认"pending" Returns: 待办事项列表 |
| check_all_remindersB | 一次性检查所有到期的提醒(闹钟和待办事项) 这是一个便捷工具,小智可以定期调用此接口来检查是否有需要提醒的内容 Returns: 包含所有到期闹钟和待办的汇总信息 |
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
Most tools have distinct purposes, but there is some overlap between 'check_all_reminders' and the individual 'get_pending_alarms' and 'get_pending_todos' tools, which could cause confusion about when to use each. However, descriptions clarify that 'check_all_reminders' is a convenience tool for periodic checks, while the others are more specific.
Tool names follow a consistent verb_noun pattern (e.g., 'add_alarm', 'complete_todo'), with only minor deviations like 'check_all_reminders' using a plural noun and 'list_todos' being slightly less descriptive. Overall, the naming is predictable and readable.
With 8 tools, the count is well-scoped for a reminder management server, covering core operations like adding, completing, listing, and dismissing reminders without being overwhelming. Each tool serves a clear purpose in the domain.
The tool set provides good coverage for reminder management, including add, complete, list, and dismiss operations for both alarms and todos. A minor gap is the lack of a tool to update existing reminders (e.g., modify alarm time or todo details), but agents can work around this by dismissing and re-adding.