mcp-supertoinette
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_recipeA | 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. |
| search_recipesA | Search Supertoinette by a dish or an ingredient. Each row carries the identifier to read the recipe with get_recipe. The site publishes no total, so 'total_available' is null and 'last_page' says how far the results run. The categories it counts beside a search are returned as 'facets': pass one back as 'category' to narrow the search, spelled exactly as the site spells it. A category the site does not know is answered like a search that matched nothing, so a filter that finds nothing is dropped and the answer says so. |
| list_categoriesA | List the categories Supertoinette browses its recipes by. Each entry carries the token that opens its listing with browse_recipes, and 'listed_in' says where the site printed it: its footer holds the kinds of dish, its menu holds the ways of cooking and the seasons. Never build a token by hand, because the site answers a number paired with the wrong name with a page it does not hold. These two lists are not every category the site files recipes under: a recipe's own tags open onto hundreds more that neither list publishes. |
| browse_recipesA | Read the recipes of one Supertoinette category, page by page. The category is a number and a name together, taken from list_categories or from the 'tags' of a recipe, and never assembled by hand. Each row carries the identifier get_recipe reads a recipe with, plus the difficulty and the total time the site prints beside it. The site publishes no total, so 'last_page' says how far the listing runs. |
| get_wine_pairingsA | Read the wines Supertoinette ranks for one dish, given the number in its address as 'id'. Each wine comes with the site's own wording for how well it goes, from 'Bon accord' to 'Accord parfait'. Called with 'page' instead, it reads one page of the alphabetical index of dishes, which is where the identifiers come from: the index runs alphabetically, so a dish beginning with a late letter sits on a late page. |
| scale_ingredientsA | Rescale a list of French ingredient lines, offline. Give either 'factor', or 'from_servings' and 'to_servings' together. Each line comes back with what was done to it: 'scaled' when the arithmetic landed exactly, 'rounded' when the value had to move to stay something a kitchen can measure out, and 'unscaled' when the line carries no quantity at all. Nothing is converted between unit systems, and an approximate measure such as a pincée keeps its own size. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a clearly distinct action: listing categories, reading a single recipe, searching recipes, browsing by category, fetching wine pairings, and scaling ingredients. The only near overlap is search vs. browse, but their descriptions make the distinction clear.
All tool names follow a consistent verb_noun snake_case pattern: list_categories, get_recipe, search_recipes, browse_recipes, get_wine_pairings, scale_ingredients. There is no mixing of styles or vague verbs.
Six tools is well-scoped for a recipe retrieval and utility server. Each tool earns its place without redundancy or bloat.
The read-only recipe domain is well covered: category discovery, search, browsing, full recipe retrieval, and wine pairing data are all present. A minor gap is that not all recipe tag categories are directly listable without first reading a recipe, but the core workflow is complete.