balanceit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BALANCEIT_EMAIL | No | Your balance.it account email. | |
| BALANCEIT_PASSWORD | No | Your balance.it account password. | |
| BALANCEIT_STATE_SEED | No | Path to a storageState export used to seed the session. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculate_caloriesB | Balance IT's daily kcal estimate for a pet given species, weight, age, and reproductive status. HTTP endpoint, sub-second. |
| search_foodsB | Fuzzy search over Balance IT's food database. Returns curated 'm*' rows plus USDA reference foods. HTTP endpoint, sub-second. |
| list_catalogueA | The complete chip catalogue for a species (79 items canine adult; 51 marked one-pot-compatible). Cached for 7 days. Browser-driven; first call ~5-8s. |
| generate_recipeA | Fill the pet profile, pick ingredient food_ids, submit, and wait for Balance IT to build N balanced recipe options. Browser-driven; typically 60-90s. Food_ids come from search_foods or list_catalogue. The response includes submitted_food_ids (ground-truth from the form) and missing_from_options (a soft signal that a requested ingredient did not appear in the built recipes; empty in the happy path). Any food_id that could not be added throws a clear error rather than silently dropping. |
| get_recipeA | Load /recipe/ and extract calories, macro split, gram-weight ingredient list, and required supplement. Browser-driven; ~5-10s. |
| session_statusA | Whether a usable balance.it session is on disk. Useful to distinguish 'dead session' from 'real failure' before running slower tools. |
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 6 tools
Each tool targets a distinct resource and action: loading a recipe, calculating calories, searching foods, listing the catalogue, generating a recipe, and checking session state. Even though get_recipe and generate_recipe both involve recipes, the load-vs-create distinction is clear from the descriptions.
Most tools follow a clear verb_noun pattern (get_recipe, calculate_calories, search_foods, list_catalogue, generate_recipe). session_status is a small deviation that reads as a state check rather than an action, but it's still understandable and consistent in style.
Six tools is a well-scoped set for a Balance It nutrition MCP. Each tool covers a core part of the workflow (estimating calories, finding ingredients, generating recipes, loading results) without being bloated or too thin.
The core lifecycle is covered: search/select ingredients, generate recipes, retrieve a specific recipe, and estimate calories. Minor gaps exist, such as no explicit recipe listing or update/delete, but these are not essential for the domain and the workflow is functional.