Save a recipe with optional ingredients, source URL, instructions and servings. Link it to a date with create_meal_plan.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Source URL. | |
| name | Yes | Recipe name. | |
| servings | No | Servings the recipe yields, minimum 1. | |
| ingredients | No | Ingredients. | |
| instructions | No | Cooking method. |
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | ||
| title | No | ||
| message | No | ||
| variant | No |
Changes observed during successful MCP inspections.
Input schema / properties / ingredients / descriptionPrevious value: -"Optional list of ingredients required for the recipe"New value: +"Ingredients."Input schema / properties / ingredients / items / descriptionAdded value: +"One ingredient and its quantity."Input schema / properties / ingredients / items / properties / name / descriptionPrevious value: -"Ingredient name"New value: +"Ingredient name."Input schema / properties / ingredients / items / properties / quantity / descriptionPrevious value: -"Whole-number quantity of the ingredient (no fractional/unit support). Minimum: 1"New value: +"Whole-number quantity, minimum 1. No fractions or units."Input schema / properties / instructions / descriptionPrevious value: -"Optional free-text cooking instructions/method"New value: +"Cooking method."Input schema / properties / instructions / examplesAdded value: +[
+ "Marinate the chicken, then simmer in the spiced tomato sauce for 20 minutes."
+]Input schema / properties / name / descriptionPrevious value: -"Recipe name/title"New value: +"Recipe name."Input schema / properties / servings / descriptionPrevious value: -"Number of servings the recipe yields. Minimum: 1"New value: +"Servings the recipe yields, minimum 1."Input schema / properties / url / descriptionPrevious value: -"Optional source URL the recipe was found at (e.g. a link to a blog or recipe site)"New value: +"Source URL."Input schema / examplesAdded 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"
+ }
+]Input schema / properties / ingredients / descriptionAdded value: +"Optional list of ingredients required for the recipe"Input schema / properties / ingredients / items / properties / name / descriptionAdded value: +"Ingredient name"Input schema / properties / ingredients / items / properties / name / examplesAdded value: +[
+ "chicken breast"
+]Input schema / properties / ingredients / items / properties / quantity / descriptionPrevious value: -"Minimum: 1"New value: +"Whole-number quantity of the ingredient (no fractional/unit support). Minimum: 1"Input schema / properties / ingredients / items / properties / quantity / examplesAdded value: +[
+ 2
+]Input schema / properties / instructions / descriptionAdded value: +"Optional free-text cooking instructions/method"Input schema / properties / name / descriptionAdded value: +"Recipe name/title"Input schema / properties / name / examplesAdded value: +[
+ "Chicken Tikka Masala"
+]Input schema / properties / servings / descriptionPrevious value: -"Minimum: 1"New value: +"Number of servings the recipe yields. Minimum: 1"Input schema / properties / servings / examplesAdded value: +[
+ 4
+]Input schema / properties / url / descriptionAdded value: +"Optional source URL the recipe was found at (e.g. a link to a blog or recipe site)"Input schema / properties / url / examplesAdded value: +[
+ "https://example.com/recipes/chicken-tikka-masala"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate this is not read-only nor destructive; the description adds that a recipe is persisted and that ingredients, source URL, instructions, and servings are optional while name is required. It also reveals that linking to a date happens through a separate tool, which is useful behavioral context beyond 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core action and optional fields, then a useful pointer to the sibling. No filler or redundant phrasing.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a creation tool with complete schema coverage and an output schema, the description covers the essentials: what is created, what is optional, and that meal-plan linking is handled elsewhere. It doesn't mention duplicate handling or constraints, but those are adequately handled by the rich schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema already documents every parameter. The description only restates that the listed fields are optional, adding no new semantics beyond the structured data.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a clear verb-resource pair ('Save a recipe') and enumerates the optional fields, so an agent knows exactly what resource this tool creates. It points to create_meal_plan for linking, which helps differentiate scope, though it doesn't contrast with update_recipe or delete_recipe.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
By instructing 'Link it to a date with create_meal_plan,' the description gives clear context on where this tool fits in the workflow and implies this tool does not perform scheduling. It lacks explicit when-not-to-use guidance, but provides enough context for an agent to choose the right tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.