claude-todo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TODO_DATA_DIR | No | Directory holding todo.db | ~/.claude-todo |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| todo_listB | List todos ordered by date (undated last), then by importance (high first). |
| todo_searchC | Case-insensitive substring search over todo slugs and prompts. |
| todo_addA | Create a todo. Fails with SLUG_EXISTS if an open todo already uses the slug; a done todo with the same slug is replaced. |
| todo_updateA | Update an existing todo, open or done. Only the fields you pass change. The slug cannot be changed. |
| todo_doneA | Mark a todo as done. Calling it on an already-done todo is a no-op and reports already_done: true. |
| todo_deleteB | Permanently delete a todo, open or done. |
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 6 tools
Each tool targets a distinct operation (list, search, add, delete, update, done) with no meaningful overlap; an agent can pick the right one unambiguously.
All names follow a consistent todo_ prefix with a short verb suffix, forming a predictable pattern throughout. The only slight quirk is todo_done being a state rather than a verb, but the convention is uniform.
Six tools is well-scoped for a todo manager, covering the core lifecycle without redundancy or bloat.
CRUD plus search and completion are covered, but there is no explicit reopen/un-done operation or single-item get, leaving a minor gap agents must work around.