Todo 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_todoA | Add a new todo item to the list. Returns the created todo with its ID. |
| list_todosA | Get all todo items as a structured list with IDs, text, completion status, and creation dates. |
| complete_todoA | Mark a todo item as done/completed by its ID. |
| delete_todoB | Remove a todo item from the list by its ID. |
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 4 tools
Each tool performs a distinct operation on todos: add, list, complete, and delete. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (add_todo, list_todos, complete_todo, delete_todo), making the API predictable.
Four tools is a well-scoped set for a todo server, covering the essential operations without unnecessary bloat.
The core lifecycle of create, read, update status, and delete is covered. The only notable gap is the lack of an update_todo tool for editing todo text, but this is minor for the domain.