Skip to main content
Glama
sheacoding

MCP Reminder

by sheacoding

complete_todo

Mark todo items as completed by matching their title or keywords, helping users track task progress in the MCP Reminder system.

Instructions

完成待办事项

通过标题关键词匹配待办事项并标记为已完成

Args: title: 待办事项标题或关键词

Returns: 操作结果

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes

Implementation Reference

  • Implementation of the complete_todo tool in the V2 MCP server.
    @mcp.tool()
    def complete_todo(title: str) -> dict:
        """
        完成待办事项
    
        通过标题关键词匹配待办事项并标记为已完成
    
        Args:
            title: 待办事项标题或关键词
    
        Returns:
            操作结果
        """
        if not title:
            return {
                "success": False,
                "error": "请提供待办事项标题或关键词"
            }
    
        # 查找待办事项
        todo = storage.find_todo_by_title(title)
        if not todo:
            return {
                "success": False,
                "error": f"未找到标题包含 '{title}' 的待办事项"
            }
    
        # 标记为已完成
        todo.status = "completed"
        storage.update_todo(todo)
    
        logger.info(f"完成待办: {todo.title}")
    
        return {
            "success": True,
            "todo_id": todo.id,
            "title": todo.title,
            "message": f"已完成待办: {todo.title}"
        }
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. It mentions marking as completed, which implies a mutation, but lacks details on permissions, error handling, or what happens if multiple todos match. This is a significant gap for a mutation tool with zero annotation coverage.

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 brief and front-loaded with the main action, followed by parameter and return notes. It avoids unnecessary fluff, though the structure could be slightly improved by integrating the Args and Returns more seamlessly.

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

Completeness2/5

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

Given no annotations, 0% schema coverage, and no output schema, the description is incomplete. It covers the basic purpose and parameter hint but lacks behavioral details, error cases, and output specifics, which are crucial for a mutation tool with siblings.

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

Parameters2/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 that 'title' is for matching by title or keywords, providing some meaning beyond the schema. However, it doesn't explain format, case sensitivity, or partial matching rules, leaving gaps for the single parameter.

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

Purpose3/5

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

The description states the tool '完成待办事项' (complete todo) and mentions matching by title keywords and marking as completed, which clarifies the verb and resource. However, it doesn't distinguish from siblings like 'list_todos' or 'add_todo', making it somewhat vague in differentiation.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for completing todos via title matching, but it doesn't specify prerequisites, exclusions, or compare to siblings like 'dismiss_alarm' or 'check_all_reminders'.

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