Tracking MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_PATH | No | Path to the SQLite database file. Auto-created on first use. | ~/tracking.db |
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 |
|---|---|
| track_eventB | Insert or update tracking event for any entity type |
| query_eventsB | Query tracking events with filters |
| delete_eventB | Delete tracking event by ID |
| list_entity_typesA | Get all registered entity types with schema examples |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| track-weight | Template for tracking body weight |
| track-workout | Template for logging workout session |
| query-trend | Get trend data for entity type over date range |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Entity Types Registry | List of all registered entity types with schema examples |
| Usage Guide | How to track new entity types dynamically |
| Tracking Summary | Current statistics (total events, entity types, date range) |
TDQS
Scored across 4 tools
Each tool targets a distinct action: deleting, tracking, querying events, or listing entity types. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., delete_event, track_event).
4 tools is well-scoped for a tracking server, covering essential operations without bloat.
Core CRUD is present (create/update via track_event, read via query_events, delete via delete_event), plus entity type discovery. Minor gap: no explicit get single event, but query_events with filters can serve that purpose.