eatmundo

Get recipe

get_recipe

Read-onlyIdempotent

Full recipe for one dish: steps, FAQ, image credit, and ingredients with PARSED quantities (amount, unit, and a normalised base in grams or millilitres where the quantity is measurable). Count-based lines like "3 onions" carry a gram estimate only where a per-item weight is known. Pass servings to rescale the ingredient quantities; the steps keep the original amounts. adaptations lists the diets (vegan, vegetarian, halal, dairy-free, pescatarian) the dish can be fully converted to, with each swap marked substitute (same dish) or adaptation (a different dish).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Language for titles, ingredient names and URLs.	en
`slug`	Yes	Recipe slug in any of the 7 languages, or a dish name (resolved by search).
`servings`	No	Rescale ingredient quantities to this many servings. The dish's own count is returned as original_servings. Steps are NOT rescaled: they keep the amounts of the original recipe.

Output Schema

TableJSON Schema

Name	Required	Description
`faq`	Yes
`url`	Yes
`form`	Yes
`slug`	Yes
`image`	Yes
`notes`	Yes
`steps`	Yes
`title`	Yes
`country`	Yes
`calories`	Yes
`category`	Yes
`servings`	Yes	Servings the ingredient quantities are for (the requested count when servings was passed).
`adaptations`	Yes	Diets this dish does not already fit but can be FULLY converted to - the adapt control shown on the recipe page. A diet is listed only when every disqualifying ingredient has a swap; partial conversions are never offered. Empty when the dish already fits every listed diet, or when no full conversion exists.
`attribution`	Yes
`description`	Yes
`ingredients`	Yes
`match_count`	Yes
`resolved_by`	Yes
`country_name`	Yes
`original_servings`	Yes	Servings the recipe was written for; the steps always describe this count.
`prep_time_minutes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 6, 2026

addedInput schema / properties / servings

Added value: +{
+  "description": "Rescale ingredient quantities to this many servings. The dish's own count is returned as original_servings. Steps are NOT rescaled: they keep the amounts of the original recipe.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / adaptations

Added value: +{
+  "description": "Diets this dish does not already fit but can be FULLY converted to - the adapt control shown on the recipe page. A diet is listed only when every disqualifying ingredient has a swap; partial conversions are never offered. Empty when the dish already fits every listed diet, or when no full conversion exists.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "diet": {
+        "enum": [
+          "vegan",
+          "vegetarian",
+          "halal",
+          "dairy-free",
+          "pescatarian"
+        ],
+        "type": "string"
+      },
+      "result": {
+        "description": "same_dish when every swap is a like-for-like substitute; different_dish when at least one swap is an adaptation.",
+        "enum": [
+          "same_dish",
+          "different_dish"
+        ],
+        "type": "string"
+      },
+      "swaps": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "ingredient": {
+              "type": "string"
+            },
+            "kind": {
+              "enum": [
+                "substitute",
+                "adaptation"
+              ],
+              "type": "string"
+            },
+            "replacement": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "ingredient",
+            "replacement",
+            "kind"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "diet",
+      "result",
+      "swaps"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / original_servings

Added value: +{
+  "description": "Servings the recipe was written for; the steps always describe this count.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / servings / description

Added value: +"Servings the ingredient quantities are for (the requested count when servings was passed)."

changedOutput schema / required

Previous value: -[
-  "slug",
-  "title",
-  "country",
-  "country_name",
-  "category",
-  "form",
-  "prep_time_minutes",
-  "url",
-  "description",
-  "calories",
-  "servings",
-  "steps",
-  "faq",
-  "ingredients",
-  "image",
-  "match_count",
-  "resolved_by",
-  "notes",
-  "attribution"
-]New value: +[
+  "slug",
+  "title",
+  "country",
+  "country_name",
+  "category",
+  "form",
+  "prep_time_minutes",
+  "url",
+  "description",
+  "calories",
+  "servings",
+  "original_servings",
+  "steps",
+  "faq",
+  "ingredients",
+  "image",
+  "adaptations",
+  "match_count",
+  "resolved_by",
+  "notes",
+  "attribution"
+]

First observedSep 10, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, not open-world), while the description discloses substantive behavior: quantities are parsed and normalised to grams/ml, count-based lines get gram estimates only when a per-item weight exists, servings rescales ingredients but NOT steps, and adaptations are tagged substitute vs adaptation. This is rich context an agent needs to interpret results correctly.

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

Conciseness4/5

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

Front-loaded with the resource and payload, then details on quantity parsing and rescaling. Dense but every clause carries information; slightly long for a single paragraph but no filler sentences.

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?

With an output schema present, return values need not be explained, yet the description still clarifies the parsed-quantity and adaptations semantics that shape interpretation. It leaves error handling (unresolvable slug, unavailable language) unexplained, a minor gap for a read-only lookup.

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?

Schema description coverage is 100%, so lang, slug and servings are already documented, including the steps-not-rescaled caveat for servings. The description largely restates that behavior; it adds little beyond the schema, so the baseline 3 applies.

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 verb+resource ('Full recipe for one dish') and enumerates the payload (steps, FAQ, image credit, parsed ingredients, adaptations), which cleanly separates it from search_dishes and compare_dishes. An agent can distinguish it from all siblings without opening the schema.

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?

Usage is implied rather than stated: the agent infers this is the detail fetch for a single dish given a slug. It explains how servings rescaling works but never says when to prefer this over siblings like search_dishes or substitute_ingredient, nor any prerequisites or exclusions.

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

All eatmundo tools Inspect

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

Need Help?