Elfy.Life

Lire une recette Elfy.Life

get_recipe

Read-onlyIdempotent

Renvoie une recette publique d'Elfy.Life (ingrédients, préparation et matériel en Markdown, durées ISO 8601, difficulté sur difficultyScale, valeurs nutritionnelles par portion, catégorie, image) avec son URL canonique. Les champs non renseignés sont omis. Les offres et inscriptions de la page (bannières, newsletter recettes) sont retirées de la préparation et de l'utilisation et listées à part dans callToActions.

Input Schema

Name	Required	Description	Default
`slug`	Yes	slug de la recette, tel que renvoyé par search_content

Output Schema

Name	Required	Description
`url`	Yes
`use`	Yes	Markdown
`image`	No
`title`	Yes
`category`	No
`cookTime`	No	durée ISO 8601
`prepTime`	No	durée ISO 8601
`equipment`	No	Markdown
`nutrition`	No	valeurs par portion
`totalTime`	No	durée ISO 8601
`difficulty`	Yes
`description`	No
`ingredients`	Yes
`preparation`	Yes	Markdown
`recipeYield`	No
`callToActions`	Yes	offres et inscriptions retirées de la préparation et de l'utilisation
`difficultyScale`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026

addedOutput schema / properties / callToActions

Added value: +{
+  "description": "offres et inscriptions retirées de la préparation et de l'utilisation",
+  "items": {
+    "properties": {
+      "label": {
+        "type": "string"
+      },
+      "url": {
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "required": [
+      "label",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "title",
-  "url",
-  "difficulty",
-  "difficultyScale",
-  "ingredients",
-  "preparation",
-  "use"
-]New value: +[
+  "title",
+  "url",
+  "difficulty",
+  "difficultyScale",
+  "ingredients",
+  "preparation",
+  "use",
+  "callToActions"
+]

Changed1 schema field changedOct 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "category": {
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "slug": {
+          "type": "string"
+        },
+        "url": {
+          "format": "uri",
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "slug",
+        "url"
+      ],
+      "type": "object"
+    },
+    "cookTime": {
+      "description": "durée ISO 8601",
+      "type": "string"
+    },
+    "description": {
+      "type": "string"
+    },
+    "difficulty": {
+      "minimum": 1,
+      "type": "integer"
+    },
+    "difficultyScale": {
+      "type": "integer"
+    },
+    "equipment": {
+      "description": "Markdown",
+      "type": "string"
+    },
+    "image": {
+      "format": "uri",
+      "type": "string"
+    },
+    "ingredients": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "nutrition": {
+      "description": "valeurs par portion",
+      "properties": {
+        "caloriesKcal": {
+          "type": "integer"
+        },
+        "fatG": {
+          "type": "number"
+        },
+        "netCarbsG": {
+          "type": "number"
+        },
+        "proteinG": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "prepTime": {
+      "description": "durée ISO 8601",
+      "type": "string"
+    },
+    "preparation": {
+      "description": "Markdown",
+      "type": "string"
+    },
+    "recipeYield": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "totalTime": {
+      "description": "durée ISO 8601",
+      "type": "string"
+    },
+    "url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "use": {
+      "description": "Markdown",
+      "type": "string"
+    }
+  },
+  "required": [
+    "title",
+    "url",
+    "difficulty",
+    "difficultyScale",
+    "ingredients",
+    "preparation",
+    "use"
+  ],
+  "type": "object"
+}

First observedOct 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world. The description adds genuinely non-obvious behavior: unset fields are omitted, and offers/newsletter CTAs are stripped out of the preparation and usage text and surfaced separately in callToActions. That materially changes how an agent should interpret the payload, though nothing is said about errors or missing slugs.

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?

Three tight sentences, front-loaded with the return contract before the field-omission and CTA caveats. The field enumeration partly duplicates what the output schema already declares, which is the only real redundancy.

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

Completeness5/5

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

With an output schema present, the description need not explain return values, yet it still covers the two non-obvious payload behaviors (omitted fields, extracted CTAs) plus the canonical URL. Combined with full annotation coverage and a fully documented single parameter, nothing needed to invoke it correctly is missing.

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 coverage is 100% and the single slug parameter is already documented in the schema, including its provenance from search_content. The description adds no additional constraint or format detail, so baseline 3 applies.

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

Purpose4/5

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

States a specific verb+resource: 'Renvoie une recette publique d'Elfy.Life' and enumerates the returned content (ingrédients, préparation, matériel, durées, difficulté, nutrition, catégorie, image, URL canonique). It is clearly a single-recipe fetch, distinct from list_recipes, but it never names the sibling alternatives explicitly.

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?

The only usage signal is the implicit pairing with search_content (the slug source), which is already stated in the schema. There is no explicit statement of when to call this versus list_recipes or search_content, so an agent must infer that this is the detail-fetch step after a search.

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

All Elfy.Life 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?