nutrients-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASTYAPI_KEY | Yes | Your TastyAPI 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
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 |
|---|---|
| analyze_food_imageA | Analyze a food image URL and return detailed nutritional information including calories, macros, vitamins, minerals, allergens, and dietary flags. |
| analyze_foodA | Get detailed nutritional information for a food item by name or description (no image needed). Returns calories, macros, vitamins, minerals, allergens, and dietary flags. |
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 2 tools
Both tools analyze food and return similar nutritional data, but they are clearly distinguished by input type: one requires an image URL and the other a text name/description. The descriptions make this distinction explicit, so an agent should be able to select the correct tool without confusion.
The tools follow a consistent verb_noun pattern: 'analyze_food' and 'analyze_food_image'. The naming is predictable and clearly indicates a shared core function with a specific modifier for the image variant.
With only two tools, the server feels thin for the domain of nutritional analysis. While both tools are useful, the minimal count limits the server's overall utility and makes it borderline appropriate for its stated purpose.
The two tools cover the two primary input methods for analyzing a food item: image and text description. However, there are minor gaps, such as no batch analysis or retrieval of nutritional data by food ID, but the core workflow of analyzing a single food item is fully supported.