tracking
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRACKING_TTL_DAYS | No | Retention days for done/error/paused sessions (default: 7) | |
| TRACKING_STATE_DIR | No | Directory for tracking state files (default: ~/.local/state/tracking/) | |
| TRACKING_TTL_RUNNING_H | No | Retention hours for orphaned running sessions (default: 24) | |
| TRACKING_TEMPLATES_FILE | No | Path to user templates JSON file (default: ~/.config/tracking/templates.json) |
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 |
|---|---|
| tracking_createA | Cree une nouvelle session de tracking. Args: name: Nom de la session (ex: "[DEV] Build worldmonitor") template: voir tracking_templates() ("free", "machine", "download", "lyra_task"...) total: Valeur totale (ex: 15300 pour 15300 MB, 6 pour 6 etapes) unit: Unite affichee (ex: " MB", " etapes") items: Liste optionnelle d'etapes [{name, status?, total?, unit?, note?}] extra: Champs specifiques au template (speed, eta, operation, target...) pid: PID du processus a signaler par tracking_stop / tracking_kill |
| tracking_updateB | Met a jour la progression d'une session. La vitesse, l'ETA et le temps
ecoule sont calcules automatiquement a partir de Args: session_id: ID de la session processed: Nouvelle valeur de progression (optionnel) message: Message de log a ajouter (optionnel) item_updates: Etapes a mettre a jour ou creer [{name?, id?, status?, processed?, note?}] extra: Champs extra a mettre a jour (speed, eta, phase...) level: Niveau du message : "info" | "warn" | "error" |
| tracking_logB | Ajoute une entree de log (info | warn | error) sans modifier la progression. |
| tracking_completeC | Marque une session comme terminee et met la progression a 100%. |
| tracking_errorC | Marque une session en erreur. |
| tracking_getC | Retourne l'etat formate complet d'une session (avec metriques). |
| tracking_listB | Liste les sessions avec filtres optionnels. Args: template: Filtrer par template ("download", "machine", "free", "movie", "lyra_task"...) status: Filtrer par statut ("running", "done", "error", "paused") |
| tracking_deleteC | Supprime une session (sans toucher au processus). |
| tracking_stopB | Arret propre : envoie SIGTERM au processus si la session a un Args: session_id: ID de la session message: Raison de l'arret (optionnel) |
| tracking_killB | Arret force : envoie SIGKILL au processus si la session a un Args: session_id: ID de la session |
| tracking_templatesA | Liste les templates disponibles (builtins + ~/.config/tracking/templates.json). |
| open_tracking_uiB | Ouvre le dashboard de tracking dans un terminal Kitty. Args: filter_template: Template a afficher au demarrage ("lyra_task", "movie", "download"...) Si absent, affiche toutes les sessions. |
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
Most tools target distinct operations, but tracking_stop, tracking_kill, tracking_delete, tracking_complete, and tracking_error form a cluster of lifecycle-ending actions that could be confused, though descriptions do differentiate them (SIGTERM+pause vs SIGKILL+delete vs delete vs complete). tracking_update vs tracking_log also slightly overlap since update can carry a message.
Nearly all tools use a consistent snake_case tracking_verb pattern (create, update, log, complete, error, get, list, delete, stop, kill). The single outlier is open_tracking_ui, which uses a different prefix style, a minor deviation.
12 tools is well within the ideal 3-15 range and each maps to a meaningful lifecycle operation for session management. No filler tools appear present.
Full lifecycle coverage exists: create, update, log, complete, error, get, list, delete, stop, kill, plus templates and UI. The main gap is an explicit resume/un-pause operation, since tracking_stop leaves a session paused with no dedicated tool to restart it.