Todo Markdown 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 |
|---|---|
| list_todosB | List all todos from the markdown file |
| add_todoC | Add a new todo item |
| update_todoC | Update an existing todo item |
| delete_todoC | Delete a todo item |
| clear_completedB | Remove all completed todo items |
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 5 tools
Each tool has a clearly distinct purpose: add, clear completed, delete, list, and update todos. There is no overlap in functionality, and an agent can easily distinguish between them based on their specific actions.
All tool names follow a consistent verb_noun pattern (e.g., add_todo, delete_todo). The naming is uniform throughout, using snake_case and clear verbs that accurately describe each action.
With 5 tools, this server is well-scoped for managing todos in a markdown file. Each tool serves a distinct and necessary function, covering core operations without being overly simplistic or bloated.
The tool set provides complete CRUD coverage for todo management: create (add_todo), read (list_todos), update (update_todo), and delete (delete_todo), plus a utility for clearing completed items. There are no obvious gaps for the intended domain.