toda
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TODA_FILE | No | Explicit path to the TODA.md ledger file. If unset, TODA.md is resolved from the session's working directory. |
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 |
|---|---|
| toda_initA | Create TODA.md for the current project (idempotent); returns the convention-file snippet |
| toda_addA | Append a deferred item to TODA.md (auto-creates the file) |
| toda_listC | List deferred items (default: open + sleeping) |
| toda_setC | Update an item status (moves it between sections) |
| toda_pruneA | Move done items older than N days into TODA-archive.md |
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 maps to a distinct action on the TODA.md lifecycle: init (create file), add (append item), list (read), set (change status), prune (archive). There is no overlap — 'add' creates items while 'set' only transitions status, and 'prune' is clearly scoped to done items.
All tools follow the exact pattern toda_<verb> in snake_case with short, predictable verbs. The shared prefix also makes the tool family easy to discover and group.
Five tools is a tight, well-scoped surface for a deferred-item tracker: one per lifecycle stage (init, add, list, update, archive). No tool feels redundant or filler.
The core lifecycle (create file, add, list, change status, archive) is covered, but there is no way to delete an item outright or edit an item's text without archiving. These are minor gaps an agent can work around by setting status or manual edits.