Unofficial Monsieur Cuisine MCP

Overview Schema Source Related Servers Discussions Admin

Search Recipes

search_recipes

Find matching Monsieur Cuisine recipes by free-text query and filters for ingredients, meal categories, nutrition, duration, and rating.

Instructions

Search Monsieur Cuisine recipes by free text and/or filters.

IMPORTANT: categories, ingredient_categories and complexity are language-dependent - their valid identifiers differ per language (e.g. category IDs and complexity labels for "pl-PL" are entirely different from "en-US"). Always call list_recipe_filters(language) first with the same language to get valid identifiers for these three arguments.

Each result includes a url field pointing at the recipe's web page - do not fetch that page directly. Instead, pass the result's id to the get_recipe tool, which returns the same data as clean JSON.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_recipes"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	1-based page number (20 results per page).
`media`	No	"video" to only return recipes with a video.
`query`	No	Free-text search term (e.g. "chicken").
`source`	No	Recipe source, one of "official" (Monsieur Cuisine) or "member" (community-submitted).
`fat_max`	No	Maximum fat per serving (g).
`fat_min`	No	Minimum fat per serving (g).
`language`	No	Result language/locale, e.g. "pl-PL", "en-US".	en-US
`categories`	No	Meal-type category IDs to filter by (e.g. main courses, desserts, vegan). Language-dependent - see list_recipe_filters.
`complexity`	No	Recipe difficulty label. Language-dependent - see list_recipe_filters (e.g. "Easy" for "en-US", "łatwe" for "pl-PL").
`rating_max`	No	Maximum average rating (0-5).
`rating_min`	No	Minimum average rating (0-5).
`sort_field`	No	Field to sort by, e.g. "lastUpdated", "rating", "popularity".	lastUpdated
`device_type`	No	Filter to a device; only "MC3.0" (Monsieur Cuisine Smart) is supported. Omit to search recipes for any device.
`protein_max`	No	Maximum protein per serving (g).
`protein_min`	No	Minimum protein per serving (g).
`calories_max`	No	Maximum energy value per serving (kcal).
`calories_min`	No	Minimum energy value per serving (kcal).
`duration_max`	No	Maximum total duration in minutes.
`duration_min`	No	Minimum total duration in minutes.
`sort_direction`	No	"ASC" or "DESC".	DESC
`carbohydrate_max`	No	Maximum carbohydrate per serving (g).
`carbohydrate_min`	No	Minimum carbohydrate per serving (g).
`ingredient_categories`	No	Ingredient category IDs to filter by (e.g. fish, beef, vegetables). Language-dependent - see list_recipe_filters.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the burden and discloses real behavioral traits: language-dependent identifier sets, a mandatory pre-call, and a warning not to fetch result URLs directly. It does not cover authentication or error behavior, so it falls short of exhaustive, but the unusual failure mode (wrong-locale identifiers returning nothing) is called out.

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 purpose, then an IMPORTANT block for the prerequisite, then a result-handling note. Three tight paragraphs with no filler, though the parenthetical Polish locale example partly duplicates the schema's own example.

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?

For a 23-parameter tool with 100% schema coverage and an output schema, the description supplies exactly the non-schema knowledge an agent needs: the locale coupling, the prerequisite call, and the correct follow-up tool for reading a result. Return-value shape is legitimately left to the output schema.

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 coverage is 100%, so baseline is 3; the description adds meaning by grouping categories/ingredient_categories/complexity as language-dependent and tying them to a required resolution step, which the schema only notes per-parameter. The remaining ~20 parameters get no additional narrative treatment.

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 and resource (search Monsieur Cuisine recipes) plus the two search modes (free text and/or filters). It is clearly distinguishable from siblings list_recipe_filters (which provides identifiers) and get_recipe (which fetches a single recipe by id), both of which are named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit prerequisite ('Always call list_recipe_filters(language) first with the *same* language') scoped to three specific arguments, and names an alternative path ('pass the result's `id` to the get_recipe tool'). This is as close to a decision rule as a search tool gets.

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