workbrain
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_contextA | Get full personal context in one call: playbook, this week's agenda, recent work log, and commits. Call at session start. |
| get_playbookA | Read how the user works: approach, bug-fix style, communication preferences. |
| update_playbookB | Update the personal playbook. Use append=true to add a section without replacing the whole file. |
| get_agendaA | Get the weekly agenda: focus items, coming up, and expected deliverables. |
| add_agenda_itemC | Add an item to the weekly agenda board. |
| update_agenda_itemB | Update an agenda item: status, estimate, title, etc. Marking done auto-logs work unless log_on_done=false. |
| delete_agenda_itemB | Remove an item from the weekly agenda. |
| rollover_agendaA | Move unfinished items from a previous week into the current week (defaults: last week → this week). |
| get_weekly_summaryA | Summary for a week: agenda stats, work log entries, and commits for that week. |
| get_work_logB | Get recent work summaries logged by Claude or hooks. |
| log_workC | Log a work summary after completing something. |
| get_commitsC | Get recent git commits recorded by the post-commit hook. |
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 12 tools
Each tool targets a distinct resource and action: agenda items have get/add/update/delete, playbook has get/update, work log has log/get, and get_context/get_weekly_summary are clearly composite views. No two tools appear to do the same thing.
All tool names follow a consistent verb_noun pattern (e.g., get_agenda, add_agenda_item, update_playbook, rollover_agenda). The verb 'rollover' is unconventional but still follows the same structure, and there is no mixing of naming styles.
12 tools is well within the ideal 3-15 range and each tool covers a distinct function needed for personal work management: playbook, agenda, work log, commits, and summaries. No tool feels redundant or missing.
The agenda has full CRUD plus rollover, playbook has read/update, and work log has log/read with summaries and commit retrieval. The main gap is that work log entries cannot be updated or deleted, which could be an issue if a log entry contains errors.