Skip to main content
Glama

haus

by app.onehaus
OverviewDiscussionsAdmin

create_meal_plan

Plan a meal for a specific date and meal type. Provide recipeId to link an existing recipe (from list_recipes) OR name for a custom meal; when recipeId is given any name is ignored and stored as null.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate, YYYY-MM-DD. Must be today or within the next 28 days, so work it out from today's date.
nameNoCustom meal name when no recipe is linked.
notesNoFree-text notes.
mealTypeYesMeal slot of the day.
recipeIdNoRecipe id from list_recipes or list_global_recipes.
servingsNoServings, 1-100.
recipeSourceNoUse 'global' when recipeId came from list_global_recipes. Defaults to 'household'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
titleNo
messageNo
variantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-09-29",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-10-01",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
  2. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-09-25",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-09-29",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
  3. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-09-24",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-09-25",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
  4. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-09-23",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-09-24",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
  5. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-09-22",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-09-23",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
  6. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-09-21",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-09-22",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
  7. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-09-20",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-09-21",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
  8. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-09-19",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-09-20",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
  9. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-09-20",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-09-19",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
  10. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-09-19",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-09-20",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
  11. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-09-18",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-09-19",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
  12. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-09-17",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-09-18",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
  13. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-09-16",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-09-17",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
  14. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-09-15",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-09-16",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
  15. Changed11 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "date": "2026-07-16",
-    "mealType": "dinner",
-    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
-    "servings": 4
-  }
-]New value: +[
+  {
+    "date": "2026-09-15",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
    • changedInput schema / properties / date / description
      Previous value: -"Date of the planned meal (format: YYYY-MM-DD). Must be from today up to four weeks ahead."New value: +"Date, YYYY-MM-DD. Must be today or within the next 28 days, so work it out from today's date."
    • removedInput schema / properties / date / examples
      Removed value: -[
-  "2026-07-16"
-]
    • changedInput schema / properties / mealType / description
      Previous value: -"Which meal slot of the day this entry occupies"New value: +"Meal slot of the day."
    • changedInput schema / properties / name / description
      Previous value: -"Custom meal name when no recipe is linked"New value: +"Custom meal name when no recipe is linked."
    • addedInput schema / properties / name / examples
      Added value: +[
+  "Leftover curry"
+]
    • changedInput schema / properties / notes / description
      Previous value: -"Optional free-text notes about the planned meal"New value: +"Free-text notes."
    • addedInput schema / properties / notes / examples
      Added value: +[
+  "Double the rice"
+]
    • changedInput schema / properties / recipeId / description
      Previous value: -"ID of an existing recipe (from list_recipes or list_global_recipes)"New value: +"Recipe id from list_recipes or list_global_recipes."
    • changedInput schema / properties / recipeSource / description
      Previous value: -"Set 'global' when recipeId refers to a Discover/global recipe (from list_global_recipes); defaults to 'household'"New value: +"Use 'global' when recipeId came from list_global_recipes. Defaults to 'household'."
    • changedInput schema / properties / servings / description
      Previous value: -"Number of servings for the planned meal. Between 1 and 100"New value: +"Servings, 1-100."
  16. Changed10 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "date": "2026-07-16",
+    "mealType": "dinner",
+    "recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
+    "servings": 4
+  }
+]
    • changedInput schema / properties / date / description
      Previous value: -"Date of the planned meal (format: YYYY-MM-DD)"New value: +"Date of the planned meal (format: YYYY-MM-DD). Must be from today up to four weeks ahead."
    • addedInput schema / properties / date / examples
      Added value: +[
+  "2026-07-16"
+]
    • addedInput schema / properties / mealType / description
      Added value: +"Which meal slot of the day this entry occupies"
    • addedInput schema / properties / mealType / examples
      Added value: +[
+  "dinner"
+]
    • addedInput schema / properties / notes / description
      Added value: +"Optional free-text notes about the planned meal"
    • addedInput schema / properties / recipeId / examples
      Added value: +[
+  "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f"
+]
    • addedInput schema / properties / recipeSource / examples
      Added value: +[
+  "household"
+]
    • changedInput schema / properties / servings / description
      Previous value: -"Between 1 and 100"New value: +"Number of servings for the planned meal. Between 1 and 100"
    • addedInput schema / properties / servings / examples
      Added value: +[
+  4
+]
  17. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses the non-obvious behavior that a provided name is ignored and stored as null when recipeId is present, which goes beyond the annotations. Since readOnlyHint=false already signals a write, and no destructive behavior is relevant, the description adds meaningful context without contradicting the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with zero filler. The purpose is front-loaded, and the behavioral nuance is tucked into the second sentence without added verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the main decision path (recipe vs custom) but omits the global recipe branch: it only mentions list_recipes, whereas the schema allows recipeId from list_global_recipes and requires recipeSource='global' in that case. With a rich output schema and 100% parameter coverage this is a minor gap, but still a real omission for an agent navigating the sibling list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with helpful descriptions, so the baseline is 3. The description adds semantic value by clarifying the mutual exclusivity and precedence between name and recipeId, and by pointing to list_recipes as the source of valid IDs. However, it does not add meaning to date, mealType, servings, or recipeSource beyond what the schema gives.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action, 'Plan a meal', with a concrete resource (a meal for a date and meal type) and immediately explains the two input modes. It is distinguishable from update_meal_plan and delete_meal_plan via create semantics, and from list_recipes by referencing it as a source rather than the target.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance for the two modes: recipeId for an existing recipe from list_recipes, name for a custom meal, and defines precedence (recipeId wins). It does not explicitly name update_meal_plan as the alternative for modifying an existing plan, but the create context and the recipe-vs-name guidance are sufficiently clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All haus toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources