skills / todo-list-mcp.md
skills / todo-list-mcp.md
A guide for small language models (4B parameters) on how to use the todo-list-mcp tools. This document explains each tool clearly, shows usage rules, gives examples, and describes practical scenarios you can use every day.
This is a todo list tool set (called "MCP server") that helps you manage tasks. You can:
You will use these tools when a user asks you to plan, organize, track, or review their tasks.
There are 10 tools in total:
| # | Tool Name | What It Does |
|---|---|---|
| 1 | create-todo | Add a new task with a title and description |
| 2 | list-todos | Show ALL tasks (done and not done) |
| 3 | get-todo | Show ONE specific task by its ID |
| 4 | update-todo | Change a task's title or description |
| 5 | complete-todo | Mark a task as done |
| 6 | delete-todo | Remove a task forever |
| 7 | search-todos-by-title | Find tasks whose title contains your search word |
| 8 | search-todos-by-date | Find tasks created on a specific date |
| 9 | list-active-todos | Show only tasks that are NOT done yet |
| 10 | summarize-active-todos | Give a short summary of tasks not done yet |
Follow these rules every time you use the tools:
create-todo ā Add a New TaskWhen to use: The user wants to add a new task.
Parameters:
title (required): Short name of the task.description (required): More details. You may use markdown.Example:
list-todos ā Show All TasksWhen to use: The user wants to see every task (done and not done).
Parameters: None.
Example:
get-todo ā Show One TaskWhen to use: The user wants details about one specific task. You need the task's ID.
Parameters:
id (required): The UUID of the task.Example:
update-todo ā Change a TaskWhen to use: The user wants to change a task's title or description.
Parameters:
id (required): The UUID of the task to update.title (optional): New title.description (optional): New description.Rule: Provide at least one of title or description.
Example:
complete-todo ā Mark a Task as DoneWhen to use: The user finished a task and wants to mark it complete.
Parameters:
id (required): The UUID of the task.Example:
delete-todo ā Remove a TaskWhen to use: The user wants to permanently remove a task.
Parameters:
id (required): The UUID of the task.Example:
search-todos-by-title ā Search by TitleWhen to use: The user wants to find tasks by a word in the title.
Parameters:
title (required): The search word or phrase.Example:
search-todos-by-date ā Search by DateWhen to use: The user wants to find tasks created on a specific date.
Parameters:
date (required): Date in YYYY-MM-DD format.Example:
list-active-todos ā Show Only Not-Done TasksWhen to use: The user wants to see only tasks that are still pending.
Parameters: None.
Example:
summarize-active-todos ā Summarize Not-Done TasksWhen to use: The user wants a quick overview of pending tasks (short, not full details).
Parameters: None.
Example:
Here are common situations where you would use these tools. Follow the steps for each scenario.
User: "I have a busy day tomorrow. Help me plan."
Steps:
list-active-todos to see what is already pending.create-todo with a clear title and description (including time or priority if mentioned).list-active-todos again to show the final plan.User: "I'm working on a project. Let me add several tasks."
Steps:
list-active-todos to check for duplicates first.create-todo for each task. Give each a clear title.list-active-todos to confirm all tasks were added.User: "I finished one task. Let me mark it done."
Steps:
list-active-todos to find the task the user is referring to.complete-todo with that task's ID.User: "Let me review what I did today."
Steps:
list-todos to show ALL tasks (including completed ones).summarize-active-todos for a quick overview of what remains.User: "What tasks did I create last Monday?"
Steps:
YYYY-MM-DD format.search-todos-by-date with that date.User: "Let me clean up. Show me all tasks about 'meeting'."
Steps:
search-todos-by-title with title: "meeting".delete-todo with confirmation.User: "I want to add more details to task abc-123."
Steps:
get-todo with the task ID to see the current content.update-todo, providing the new description (or title).User: "Give me a weekly summary of my tasks."
Steps:
list-todos to get all tasks.summarize-active-todos for the pending items.| What You Need | Use This Tool |
|---|---|
| Add a task | create-todo |
| See everything | list-todos |
| See only pending tasks | list-active-todos |
| See one task's details | get-todo |
| Change a task | update-todo |
| Mark done | complete-todo |
| Delete a task | delete-todo |
| Find by title word | search-todos-by-title |
| Find by creation date | search-todos-by-date |
| Quick summary of pending | summarize-active-todos |
search-todos-by-title returns too many or too few results, try a different search word.This skill document is designed for 4B-parameter language models. It uses simple language, clear steps, and practical examples to make task management easy and reliable.
A guide for small language models (4B parameters) on how to use the todo-list-mcp tools. This document explains each tool clearly, shows usage rules, gives examples, and describes practical scenarios you can use every day.
This is a todo list tool set (called "MCP server") that helps you manage tasks. You can:
You will use these tools when a user asks you to plan, organize, track, or review their tasks.
There are 10 tools in total:
| # | Tool Name | What It Does |
|---|---|---|
| 1 | create-todo | Add a new task with a title and description |
| 2 | list-todos | Show ALL tasks (done and not done) |
| 3 | get-todo | Show ONE specific task by its ID |
| 4 | update-todo | Change a task's title or description |
| 5 | complete-todo | Mark a task as done |
| 6 | delete-todo | Remove a task forever |
| 7 | search-todos-by-title | Find tasks whose title contains your search word |
| 8 | search-todos-by-date | Find tasks created on a specific date |
| 9 | list-active-todos | Show only tasks that are NOT done yet |
| 10 | summarize-active-todos | Give a short summary of tasks not done yet |
Follow these rules every time you use the tools:
create-todo ā Add a New TaskWhen to use: The user wants to add a new task.
Parameters:
title (required): Short name of the task.description (required): More details. You may use markdown.Example:
list-todos ā Show All TasksWhen to use: The user wants to see every task (done and not done).
Parameters: None.
Example:
get-todo ā Show One TaskWhen to use: The user wants details about one specific task. You need the task's ID.
Parameters:
id (required): The UUID of the task.Example:
update-todo ā Change a TaskWhen to use: The user wants to change a task's title or description.
Parameters:
id (required): The UUID of the task to update.title (optional): New title.description (optional): New description.Rule: Provide at least one of title or description.
Example:
complete-todo ā Mark a Task as DoneWhen to use: The user finished a task and wants to mark it complete.
Parameters:
id (required): The UUID of the task.Example:
delete-todo ā Remove a TaskWhen to use: The user wants to permanently remove a task.
Parameters:
id (required): The UUID of the task.Example:
search-todos-by-title ā Search by TitleWhen to use: The user wants to find tasks by a word in the title.
Parameters:
title (required): The search word or phrase.Example:
search-todos-by-date ā Search by DateWhen to use: The user wants to find tasks created on a specific date.
Parameters:
date (required): Date in YYYY-MM-DD format.Example:
list-active-todos ā Show Only Not-Done TasksWhen to use: The user wants to see only tasks that are still pending.
Parameters: None.
Example:
summarize-active-todos ā Summarize Not-Done TasksWhen to use: The user wants a quick overview of pending tasks (short, not full details).
Parameters: None.
Example:
Here are common situations where you would use these tools. Follow the steps for each scenario.
User: "I have a busy day tomorrow. Help me plan."
Steps:
list-active-todos to see what is already pending.create-todo with a clear title and description (including time or priority if mentioned).list-active-todos again to show the final plan.User: "I'm working on a project. Let me add several tasks."
Steps:
list-active-todos to check for duplicates first.create-todo for each task. Give each a clear title.list-active-todos to confirm all tasks were added.User: "I finished one task. Let me mark it done."
Steps:
list-active-todos to find the task the user is referring to.complete-todo with that task's ID.User: "Let me review what I did today."
Steps:
list-todos to show ALL tasks (including completed ones).summarize-active-todos for a quick overview of what remains.User: "What tasks did I create last Monday?"
Steps:
YYYY-MM-DD format.search-todos-by-date with that date.User: "Let me clean up. Show me all tasks about 'meeting'."
Steps:
search-todos-by-title with title: "meeting".delete-todo with confirmation.User: "I want to add more details to task abc-123."
Steps:
get-todo with the task ID to see the current content.update-todo, providing the new description (or title).User: "Give me a weekly summary of my tasks."
Steps:
list-todos to get all tasks.summarize-active-todos for the pending items.| What You Need | Use This Tool |
|---|---|
| Add a task | create-todo |
| See everything | list-todos |
| See only pending tasks | list-active-todos |
| See one task's details | get-todo |
| Change a task | update-todo |
| Mark done | complete-todo |
| Delete a task | delete-todo |
| Find by title word | search-todos-by-title |
| Find by creation date | search-todos-by-date |
| Quick summary of pending | summarize-active-todos |
search-todos-by-title returns too many or too few results, try a different search word.This skill document is designed for 4B-parameter language models. It uses simple language, clear steps, and practical examples to make task management easy and reliable.
Always read first. Before making changes, check what tasks already exist. Use list-todos or list-active-todos to see the current state.
Use IDs to identify tasks. Each task has a unique ID (a long string of letters and numbers). To update, complete, or delete a task, you MUST provide its ID.
Title is required for create-todo. Every new task needs a title. The description is also required and can include markdown (like # headings, - lists, **bold**).
At least one field for update-todo. When updating, you must provide at least one of: title or description. You cannot update with nothing.
Date format for search-todos-by-date. Use YYYY-MM-DD format. Example: 2025-01-15 (not "January 15" or "01/15/2025").
Search is partial and case-insensitive. search-todos-by-title with the word "meeting" will find tasks with "Meeting", "team meeting", "meeting notes", etc.
Be careful with delete-todo. Deletion is permanent. Confirm with the user before deleting, especially if the task list is long.
Use list-active-todos for current work. When the user asks about what they need to do, use list-active-todos (only not-done tasks) instead of list-todos (all tasks). This keeps the list clean.
Return clear results. After using a tool, summarize the result in plain language for the user.
User: "Add a task to buy groceries tonight."
You: Use create-todo
title: "Buy groceries"
description: "Buy groceries for dinner tonight. Items: vegetables, rice, chicken."
User: "Show me all my tasks."
You: Use list-todos
ā Returns a formatted list of all tasks.
User: "Show me the details of task abc-123."
You: Use get-todo
id: "abc-123"
User: "Change the title of task abc-123 to 'Buy groceries for dinner'."
You: Use update-todo
id: "abc-123"
title: "Buy groceries for dinner"
User: "I finished reading the book. Mark it done."
You: Use complete-todo
id: "abc-123"
User: "Delete task abc-123."
You: First check the task exists (use get-todo), then use delete-todo
id: "abc-123"
User: "Find tasks about 'meeting'."
You: Use search-todos-by-title
title: "meeting"
ā Returns all tasks whose title contains "meeting" (any case).
User: "Show me tasks I created on 2025-01-15."
You: Use search-todos-by-date
date: "2025-01-15"
User: "What do I still need to do?"
You: Use list-active-todos
ā Returns only tasks that are NOT completed.
User: "Give me a quick summary of my pending tasks."
You: Use summarize-active-todos
ā Returns a short summary with count and task titles.
Always read first. Before making changes, check what tasks already exist. Use list-todos or list-active-todos to see the current state.
Use IDs to identify tasks. Each task has a unique ID (a long string of letters and numbers). To update, complete, or delete a task, you MUST provide its ID.
Title is required for create-todo. Every new task needs a title. The description is also required and can include markdown (like # headings, - lists, **bold**).
At least one field for update-todo. When updating, you must provide at least one of: title or description. You cannot update with nothing.
Date format for search-todos-by-date. Use YYYY-MM-DD format. Example: 2025-01-15 (not "January 15" or "01/15/2025").
Search is partial and case-insensitive. search-todos-by-title with the word "meeting" will find tasks with "Meeting", "team meeting", "meeting notes", etc.
Be careful with delete-todo. Deletion is permanent. Confirm with the user before deleting, especially if the task list is long.
Use list-active-todos for current work. When the user asks about what they need to do, use list-active-todos (only not-done tasks) instead of list-todos (all tasks). This keeps the list clean.
Return clear results. After using a tool, summarize the result in plain language for the user.
User: "Add a task to buy groceries tonight."
You: Use create-todo
title: "Buy groceries"
description: "Buy groceries for dinner tonight. Items: vegetables, rice, chicken."
User: "Show me all my tasks."
You: Use list-todos
ā Returns a formatted list of all tasks.
User: "Show me the details of task abc-123."
You: Use get-todo
id: "abc-123"
User: "Change the title of task abc-123 to 'Buy groceries for dinner'."
You: Use update-todo
id: "abc-123"
title: "Buy groceries for dinner"
User: "I finished reading the book. Mark it done."
You: Use complete-todo
id: "abc-123"
User: "Delete task abc-123."
You: First check the task exists (use get-todo), then use delete-todo
id: "abc-123"
User: "Find tasks about 'meeting'."
You: Use search-todos-by-title
title: "meeting"
ā Returns all tasks whose title contains "meeting" (any case).
User: "Show me tasks I created on 2025-01-15."
You: Use search-todos-by-date
date: "2025-01-15"
User: "What do I still need to do?"
You: Use list-active-todos
ā Returns only tasks that are NOT completed.
User: "Give me a quick summary of my pending tasks."
You: Use summarize-active-todos
ā Returns a short summary with count and task titles.