Skip to main content
Glama
sheacoding

MCP Reminder

by sheacoding

add_todo

Create a new reminder or task with optional description and natural language time parsing for automated notifications.

Instructions

添加待办事项

Args: title: 待办事项标题 remind_time: 提醒时间(可选),支持自然语言如"明天下午3点" description: 待办事项描述(可选)

Returns: 包含待办ID和确认信息的字典

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
remind_timeNo
descriptionNo

Implementation Reference

  • The `add_todo` tool handler, registered with the MCP server, responsible for parsing the reminder time, creating a `Todo` object, and persisting it via the storage layer.
    @mcp.tool()
    def add_todo(title: str, remind_time: str = "", description: str = "") -> dict:
        """
        添加待办事项
    
        Args:
            title: 待办事项标题
            remind_time: 提醒时间(可选),支持自然语言如"明天下午3点"
            description: 待办事项描述(可选)
    
        Returns:
            包含待办ID和确认信息的字典
        """
        if not title:
            return {
                "success": False,
                "error": "待办事项标题不能为空"
            }
    
        # 解析提醒时间
        parsed_remind_time = None
        if remind_time:
            parsed_remind_time = parse_time(remind_time)
            if not parsed_remind_time:
                return {
                    "success": False,
                    "error": f"无法解析提醒时间: {remind_time}"
                }
    
        # 创建待办事项
        todo = Todo(
            title=title,
            description=description,
            remind_time=parsed_remind_time
        )
    
        # 保存待办
        storage.add_todo(todo)
    
        logger.info(f"添加待办: {todo.title}, 提醒时间: {todo.remind_time}")
    
        message = f"已添加待办: {title}"
        if parsed_remind_time:
            message += f",将在 {parsed_remind_time} 提醒"
    
        return {
            "success": True,
            "todo_id": todo.id,
            "title": todo.title,
            "remind_time": todo.remind_time,
            "message": message
        }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that 'remind_time' supports natural language like '明天下午3点' (tomorrow at 3 PM), which adds some context about input flexibility. However, it doesn't describe what happens after creation (e.g., persistence, notifications, error handling), permissions needed, or rate limits, leaving significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and well-structured with clear sections for Args and Returns. Each sentence adds value: the purpose statement is direct, and parameter explanations are efficient. However, the 'Returns' section could be more specific, and there's some redundancy in labeling (e.g., '待办事项' repeated).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and 3 parameters with 0% schema coverage, the description is moderately complete. It covers parameter semantics well but lacks behavioral details (e.g., what '添加' entails operationally) and doesn't fully explain the return value beyond a vague '字典' (dictionary). For a mutation tool, this leaves room for improvement in safety and outcome clarity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It adds meaningful semantics: it explains that 'title' is required and what it represents, clarifies that 'remind_time' is optional and supports natural language input, and notes that 'description' is optional. This goes beyond the basic schema, providing practical usage information for all parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb '添加' (add) and resource '待办事项' (todo item), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'add_alarm' or 'complete_todo', which would require more specific context about what makes a todo distinct from an alarm or other todo-related operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose 'add_todo' over 'add_alarm' or how it relates to other todo tools like 'list_todos' or 'complete_todo'. There's no information about prerequisites, context, or exclusions for usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sheacoding/mcp-reminder'

If you have feedback or need assistance with the MCP directory API, please join our Discord server