Lecka Nutrition Race Planner
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_productsA | Returns the Lecka product catalog. Use to find products by type, caffeine content, or dual-transporter status. All filters are optional. |
| calculate_fueling_planA | Calculates personalised race nutrition targets (carbs, sodium, fluid) for an endurance athlete and returns a list of Lecka products that match the target. Use this when an athlete asks what to eat during a race, how many gels they need, or what their carb target should be. |
| get_nutrition_dataA | Returns full nutritional information and regional pricing for a specific Lecka product. Use the product ID from get_products. |
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 has a clear and distinct purpose: calculating a fueling plan, retrieving product nutrition data, and listing products. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern using snake_case (e.g., calculate_fueling_plan, get_nutrition_data, get_products), making them predictable.
With only 3 tools, the set is minimal but still covers the core needs for the narrow domain of race nutrition planning using Lecka products. Slightly under but reasonable.
The tools cover product discovery, detailed nutrition info, and plan calculation. Minor gaps exist (e.g., no user profile or plan adjustment tools), but the essential workflow is supported.