todo-demo
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_todoA | Create a new todo item and return it. |
| list_todosA | List todo items, optionally filtered by status. |
| complete_todoA | Mark one todo item as done by id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan_my_day | Create instructions for planning the open todo items. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| all-todos | A read-only JSON snapshot of all todo items. |
TDQS
Scored across 3 tools
Each tool maps to a distinct action on todos: create, list, and mark complete. There is no overlap or ambiguity between them.
All tool names follow a clear verb_noun snake_case pattern (add_todo, list_todos, complete_todo). The singular/plural variation is natural and does not affect consistency.
Three tools is a well-scoped size for a simple todo demo server. Each tool serves a clear purpose with no filler.
Core todo workflow is covered: create, list/filter, and complete. Minor gaps like deleting or editing todos exist, but they are not fatal for a demo-focused server.