Calorie-Tracking
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_mealC | Log a meal with food items and calories |
| get_daily_summaryC | Get today's calorie intake summary |
| get_weekly_reportC | Get weekly calorie consumption report |
| search_foodC | Search for calorie information of a specific food |
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 4 tools
Each tool has a clearly distinct purpose: logging meals, retrieving daily summaries, generating weekly reports, and searching food data. There is no overlap in functionality, making it easy for an agent to select the right tool without confusion.
All tools follow a consistent verb_noun naming pattern (e.g., add_meal, get_daily_summary, get_weekly_report, search_food). This uniformity enhances readability and predictability for agents using the toolset.
With 4 tools, the server is well-scoped for calorie tracking, covering core operations like logging, daily and weekly summaries, and food search. Each tool earns its place without being excessive or insufficient for the domain.
The toolset covers essential CRUD-like operations for calorie tracking, including logging and retrieval. A minor gap exists in update or delete functionality for logged meals, but agents can likely work around this for basic tracking needs.