haus

create_recipe

Create a new recipe in the household's recipe collection, with optional ingredients, source URL, instructions and serving size. Link it to a date with create_meal_plan, or browse it later with list_recipes.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Optional source URL the recipe was found at (e.g. a link to a blog or recipe site)
`name`	Yes	Recipe name/title
`servings`	No	Number of servings the recipe yields. Minimum: 1
`ingredients`	No	Optional list of ingredients required for the recipe
`instructions`	No	Optional free-text cooking instructions/method

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`title`	No
`message`	No
`variant`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed13 schema fields changedJul 14, 2026

addedInput schema / examples

Added value: +[
+  {
+    "ingredients": [
+      {
+        "name": "chicken breast",
+        "quantity": 2
+      },
+      {
+        "name": "tomato",
+        "quantity": 4
+      }
+    ],
+    "instructions": "Marinate the chicken, then simmer in the spiced tomato sauce for 20 minutes.",
+    "name": "Chicken Tikka Masala",
+    "servings": 4,
+    "url": "https://example.com/recipes/chicken-tikka-masala"
+  }
+]

addedInput schema / properties / ingredients / description

Added value: +"Optional list of ingredients required for the recipe"

addedInput schema / properties / ingredients / items / properties / name / description
```
Added value: +"Ingredient name"
```
addedInput schema / properties / ingredients / items / properties / name / examples
```
Added value: +[
+  "chicken breast"
+]
```

changedInput schema / properties / ingredients / items / properties / quantity / description

Previous value: -"Minimum: 1"New value: +"Whole-number quantity of the ingredient (no fractional/unit support). Minimum: 1"

addedInput schema / properties / ingredients / items / properties / quantity / examples
```
Added value: +[
+  2
+]
```

addedInput schema / properties / instructions / description

Added value: +"Optional free-text cooking instructions/method"

addedInput schema / properties / name / description
```
Added value: +"Recipe name/title"
```
addedInput schema / properties / name / examples
```
Added value: +[
+  "Chicken Tikka Masala"
+]
```

changedInput schema / properties / servings / description

Previous value: -"Minimum: 1"New value: +"Number of servings the recipe yields. Minimum: 1"

addedInput schema / properties / servings / examples
```
Added value: +[
+  4
+]
```

addedInput schema / properties / url / description

Added value: +"Optional source URL the recipe was found at (e.g. a link to a blog or recipe site)"

addedInput schema / properties / url / examples

Added value: +[
+  "https://example.com/recipes/chicken-tikka-masala"
+]

First observedJun 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The annotations already indicate this is a non-destructive write operation (readOnlyHint=false, destructiveHint=false). The description adds the 'household's recipe collection' scope, which is useful context, but it does not disclose other behavioral traits such as name uniqueness requirements, potential errors, or permission needs. No contradiction with 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?

The description is two short sentences. The first sentence directly states the action and optional parameters; the second gives workflow context by naming related tools. There is no redundancy or unnecessary detail.

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?

Given the tool's simplicity, full schema coverage, and the presence of an output schema, the description is sufficient. It clearly explains what the tool does and how it relates to meal planning and recipe browsing, but it could add a note about duplicate names or other edge-case behaviors for completeness.

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

Parameters3/5

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

The input schema has 100% parameter description coverage, so the description doesn't need to explain the parameters. It merely lists the optional fields (ingredients, source URL, instructions, serving size), which adds no new meaning beyond what's already in the schema property descriptions.

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?

The description clearly identifies the verb ('Create'), the resource ('a new recipe'), and the scope ('household's recipe collection'). It also distinguishes the tool from siblings by mentioning create_meal_plan and list_recipes, which shows how it fits into the workflow.

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

Usage Guidelines3/5

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

It provides context that after creating, you can link the recipe with create_meal_plan or browse with list_recipes, but it does not explicitly state when to use this tool versus alternatives like update_recipe or delete_recipe. There is no clear when-not-to-use guidance.

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

All haus tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation5/5

Each tool targets a distinct resource and action, with clear descriptions separating similar-sounding tools like create_calendar_event vs create_recurring_calendar_event. Shopping list operations (add, buy, remove, update) are clearly delineated.

Naming Consistency5/5

All tools follow a verb_noun snake_case pattern: create_*, list_*, update_*, delete_*, get_*, etc. Even special operations like store_memory, recall_memory, and skip_recommendation fit the pattern.

Tool Count1/5

With 68 tools, this server vastly exceeds a reasonable scope; the instruction manual indicates 50+ tools is an extreme mismatch. The breadth suggests the server should be split into focused sub-servers (tasks, shopping, calendar, etc.) rather than a single monolithic interface.

Completeness5/5

The tool surface covers full CRUD/lifecycle for all major resources: tasks, shopping, calendar, contacts, documents, appliances, vehicles, pets, recipes, meal plans, subscriptions, and memories. Additional features like house review, weather, and profile round out the household management domain.

Resources

Need Help?