Gamito
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GAMITO_DB | No | SQLite store path | ./gamito.db |
| GAMITO_DATA_DIR | No | Dataset and index root | ./data |
| GAMITO_INDEX_DIR | No | Prebuilt retrieval index | ./data/index |
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 |
|---|---|
| swap_mealC | Swap a plan slot to the best local recipe for an English query. |
| rescale_mealC | Rescale a persisted meal slot to a new serving count. |
| rate_mealC | Store a per-meal rating and apply deterministic tag deltas. |
| generate_meal_planC | Generate and persist a deterministic meal plan. |
| get_meal_planB | Return a stored meal plan, accepting plan_id='latest' with profile_id. |
| search_recipesC | Search the local recipe index with optional profile hard filters. |
| label_planC | Attach a short label and/or favorite flag to a persisted plan. |
| list_plansC | List persisted plans for a profile with average meal ratings. |
| regenerate_planC | Generate a new plan from a previous plan using ratings or overrides. |
| get_shopping_listC | Return a rebuilt shopping list for a persisted plan. |
| get_pantryC | Return canonical pantry staples for a profile. |
| update_pantryC | Canonicalise and update slow-use pantry staples. |
| list_profilesA | List household profiles in stable display order. |
| get_profileC | Return a full persisted profile summary. |
| save_profileC | Create or update a profile from flat MCP parameters. |
| update_preferencesC | Apply conversational preference deltas to profile tags. |
| add_recipeC | Save a structured household recipe and make it searchable. |
| update_recipeC | Patch a custom recipe and refresh its embedding when needed. |
| delete_recipeA | Delete a custom recipe, optionally orphaning historical plan references. |
| list_custom_recipesC | List saved household recipes for disambiguation and browsing. |
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 20 tools
Each tool targets a distinct resource-action combination (e.g., plan, recipe, profile, pantry). No two tools have overlapping purposes; even related tools like get_meal_plan and list_plans are clearly differentiated by specificity.
All tools follow a consistent verb_noun pattern with lowercase underscores. Verbs are imperative and nouns are singular or plural where appropriate, making the intent predictable and scannable.
With 20 tools covering recipes, meal plans, profiles, preferences, pantry, and shopping lists, the count is well-scoped for a comprehensive meal planning server. Each tool serves a clear purpose without unnecessary bloat.
The tool surface covers core CRUD and lifecycle operations for recipes, plans, profiles, and pantry. Minor gaps exist (no explicit delete for plans or profiles, no rating removal), but these are manageable for typical workflows.