GoalTrack
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_goalC | Create a new daily goal to track. direction: 'at_least' (hit at least the target, e.g. water/steps) or 'at_most' (stay at or under the target, e.g. screen time). threshold_pct: how strict 'met' is. For at_least, % of target required. For at_most, 100 = no slack, lower = more allowed slack. timezone_name: IANA tz string, e.g. 'Asia/Karachi', 'America/New_York'. |
| edit_goalB | Update any field on an existing goal. Only provided fields change. |
| delete_goalA | Remove a goal. By default soft-deletes (active=0, history kept). Pass hard_delete=True to permanently remove the goal AND its entries. |
| list_goalsB | List goals with today's progress inline for each. |
| log_entryB | Log an amount against a goal. logged_at is an ISO-8601 UTC datetime string (e.g. '2026-09-11T14:30:00Z'); defaults to now if omitted. |
| edit_entryC | Fix a mislogged entry's amount. |
| delete_entryC | Remove a logged entry entirely. |
| get_progressB | Today's total vs target for one goal, with % complete. |
| historyB | Daily totals and met/not-met status for a goal over the last N days (including today, which is always shown as in-progress rather than met/failed). |
| streak_statusB | Current and longest streak for a goal (streaks measured in days met). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily_encouragement_prompt | Ask the assistant to write a short, encouraging nudge about today's progress. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| goal_templates | A library of common goal presets (name/unit/target/direction) that an LLM can suggest when a user describes a goal in plain language. |
TDQS
Scored across 10 tools
Each tool targets a clearly distinct operation: goal CRUD, entry logging/editing/deleting, and progress/history/streak retrieval. Although list_goals includes today's progress inline, it clearly differs in scope from get_progress, which focuses on a single goal. No two tools appear interchangeable.
All names use snake_case consistently, and most follow a verb_noun pattern (add_goal, edit_goal, log_entry, get_progress). Minor deviation: history and streak_status are noun-only, but they remain readable and unambiguous.
With 10 tools, the set is well-scoped for a goal-tracking server. Each tool covers a necessary operation in the goal/entry lifecycle, and there is no redundant or filler tool.
The surface covers full CRUD for both goals and entries, plus derived analytics like progress, history, and streaks. No obvious gaps remain for the stated daily-goal tracking purpose.