psyrotrack
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_userA | Run this ON FIRST INSTALL. Ask user: 'Do you want to use default Psyro protocols or create your own?'. Use this tool to initialize the local tracker. |
| add_protocolC | Add a new protocol to track. |
| remove_protocolB | Remove a protocol by its ID. |
| set_protocolsA | Replace all current protocols with a completely new list. |
| tick_protocolA | Mark a protocol as done (or toggle off) for a specific date (YYYY-MM-DD). |
| show_trackerB | Show the tracker progress for a specific month. |
| show_statsB | Calculate and show streaks and completion percentages. |
| reset_trackerC | Clear all ticks and reset the tracker to factory settings. |
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 8 tools
Tools are mostly distinct: show_tracker and show_stats both display information but one is progress per month and the other is streaks/completion, which could be slightly confused. The protocol management tools (add/remove/set) and tick/reset are clearly separated.
Most tools follow a verb_noun pattern (show_tracker, show_stats, reset_tracker, add_protocol, remove_protocol, tick_protocol). init_user and set_protocols are also verb_noun, so the pattern is consistent, though init_user is more of a setup action than a resource operation.
8 tools is well-scoped for a personal tracking server: initialization, protocol management, ticking, and stats/reporting. Each tool serves a distinct function without redundancy.
The surface covers the core lifecycle: init, add/remove/replace protocols, tick, reset, and view progress/stats. A minor gap is the lack of an explicit way to view or edit a single protocol's details, but the set is otherwise complete for the domain.