FitTrack MCP Server
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_userA | Returns the full name of the authenticated FitTrack user. No inputs required. |
| get_mealsA | Returns meals for the authenticated FitTrack user. Optional inputs: date as YYYY-MM-DD, calories_min, and calories_max. If date is omitted, today's date is used. If no calorie range is provided, only meals with calories greater than zero are returned. |
| get_sleepA | Returns sleep entries for the authenticated FitTrack user. Optional inputs: date as YYYY-MM-DD, hours_min, and hours_max. If date is omitted, today's date is used. If no sleep-hours range is provided, only entries with hours greater than zero are returned. |
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 3 tools
Each tool targets a distinct resource: meals, sleep, and user info. There is no overlap in purpose, ensuring clear selection by an agent.
All tool names follow a consistent 'get_' prefix with a noun (get_meals, get_sleep, get_user). No mixing of conventions.
With only 3 tools, the server feels slightly thin but still appropriate for a focused read-only fitness data retrieval service. The scope is limited but coherent.
The server only provides read operations (GET) with no ability to create, update, or delete data. For a fitness tracker, this is a significant gap, limiting agent capabilities to querying existing data.