Todo List MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_todoC | Create a new todo item with validation |
| update_todoC | Update an existing todo item |
| delete_todoC | Delete a todo item |
| list_todosC | List todos with filtering and pagination |
| get_todoC | Get a specific todo by ID |
| search_todosC | Search todos by title or description |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| todo-summary | Gera um resumo analítico dos todos com estatísticas avançadas |
| todo-prioritization | Sugere priorização inteligente dos todos baseada em múltiplos critérios |
| todo-insights | Fornece insights detalhados sobre padrões de produtividade |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| All Todos | Complete list of all todos with full details |
| Todo Statistics | Statistics about todos (total, completed, pending) |
| Completed Todos | Only completed todos |
| Pending Todos | Only pending todos |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no ambiguity. The tools cover specific operations: create, delete, get, list, search, and update, with no overlap in functionality. The descriptions reinforce distinct roles, such as 'list_todos' for filtering/pagination versus 'search_todos' for title/description searches.
All tool names follow a consistent verb_noun pattern with 'todo' as the noun, using snake_case uniformly (e.g., create_todo, delete_todo). There are no deviations in naming conventions, making the set predictable and easy to understand at a glance.
With 6 tools, the count is well-scoped for a todo list server, covering essential CRUD operations and additional utilities like search. Each tool earns its place without redundancy, fitting a typical range of 3-15 tools for such a domain.
The tool surface provides complete CRUD/lifecycle coverage for todo items, including create, read (get/list/search), update, and delete. There are no obvious gaps; agents can perform all core operations without dead ends, ensuring smooth workflows.