mcp-supertoinette

Read one recipe

get_recipe

Read-onlyIdempotent

Get a Supertoinette recipe by ID: ingredients, steps, times, difficulty, cost. Rescale quantities to a serving count, adjusting to kitchen-measurable amounts.

Instructions

Read one recipe on Supertoinette by its identifier, which is the number in its address: 4210 in /recette/4210/veloute-de-gaverole.html. Returns the ingredients, the steps, the times, the difficulty and the cost the site publishes. A time the site does not publish comes back as null rather than as zero. Pass 'servings' to rescale the quantities: each line then says whether the arithmetic landed exactly, or had to move to stay an amount a kitchen can measure out.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	The number in the recipe's address, such as '4210'. Search for a dish when you do not have one.
`servings`	No	Rescale the quantities to this many. Left out, they come back as the site published them. It is refused when the site's own wording carries no number to scale from.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`faq`	Yes
`url`	Yes	The public page. Show this when citing the recipe.
`tags`	Yes
`intro`	Yes	The prose the page prints above the steps.
`notes`	Yes
`steps`	Yes
`title`	Yes	The title with the pictogram the site opens it with taken off.
`yield`	Yes	How many the recipe was written for, and how many were asked for.
`author`	Yes
`images`	Yes
`rating`	Yes
`source`	Yes
`category`	Yes
`nutrition`	Yes	Supertoinette publishes none.
`cost_level`	Yes	The site's own wording, with the scale it draws the symbols on.
`difficulty`	Yes	The site's own wording. It publishes no scale for this, so none is stated.
`description`	Yes
`ingredients`	Yes
`cook_minutes`	Yes	Null when the site publishes no cooking time.
`prep_minutes`	Yes	Null when the site publishes no preparation time.
`published_at`	Yes
`rest_minutes`	Yes	Resting time, which the page prints as 'Pause'.
`total_minutes`	Yes
`ingredient_count`	Yes	Lines rendered, headings included.
`ingredient_sheets`	Yes
`title_as_published`	Yes	The title exactly as the site wrote it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedv1.1.0Sep 11, 2026
- removedOutput schema / properties / author / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / author / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / category / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / category / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / description / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / ingredients / items / properties / amount / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / ingredients / items / properties / amount / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / ingredients / items / properties / amount_max / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / ingredients / items / properties / amount_max / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / ingredients / items / properties / unit / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / ingredients / items / properties / unit / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / intro / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / intro / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / published_at / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / published_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / tags / items / properties / category / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / tags / items / properties / category / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / yield / properties / unit / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / yield / properties / unit / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedv1.0.1Aug 28, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and idempotent annotations, the description discloses specific behaviors: missing times return null instead of zero, and rescaling reports whether arithmetic landed exactly or required rounding to measurable amounts. These details add genuine value beyond what annotations convey, with no contradiction.

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 sentences, front-loaded with purpose and identifier format, then packed with behavioral notes. No filler—every sentence and clause contributes actionable information.

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 a detailed output schema present and annotations covering safety, the description adequately covers what an agent needs to call the tool: identifier extraction, handling of missing data, and optional rescaling behavior. No critical gaps remain.

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 description coverage is 100%, so parameters are already well-documented. The description adds extra nuance for 'servings' (rounding behavior, refusal condition) and clarifies id format with a concrete example. This enriches the schema but is not essential, hence slightly above the baseline of 3.

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 states 'Read one recipe on Supertoinette by its identifier' with a concrete example of the address format. It clearly differentiates from siblings like search or browse by focusing on single-recipe retrieval and enumerates returned fields (ingredients, steps, times, difficulty, cost).

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?

The description gives clear context: use the id from the URL and optionally pass 'servings' to rescale. It also notes when servings is refused (no scaling number in site wording) and suggests 'Search for a dish when you do not have one' in the parameter schema, acting as an alternative pointer. However, it does not explicitly list exclusions or compare to each sibling, leaving room for slight ambiguity.

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

Deploy Server