Unofficial Monsieur Cuisine MCP

Overview Schema Source Related Servers Discussions Admin

List Recipe Creation Options

list_recipe_creation_options

Retrieve valid language-specific option IDs for recipe creation before calling create_recipe, so complexity and category selections match the selected locale. Requires a saved login session.

Instructions

List the valid option identifiers for creating a recipe in a given language: complexity levels, categories, serving units, ingredient units and device types.

Call this before create_recipe whenever you need to set complexity_id or category_ids, since their valid ids are language-specific and differ between locales.

Requires a saved login session: run uv run monsieur-cuisine-mcp-login once beforehand. If no session is saved, this tool raises an error telling the user to do that.

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": "list_recipe_creation_options"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Locale to fetch options for, e.g. "pl-PL", "en-US". Must match the `language` you intend to pass to create_recipe.	en-US

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it discloses the saved-login prerequisite, the login command to run, and the error behavior when no session exists. It does not explicitly label the operation as read-only, though 'List' strongly implies it.

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 short and front-loaded: purpose first, then the pre-call relationship to create_recipe, then the login prerequisite. Each sentence adds useful information with no repetition.

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?

Given one simple parameter, an output schema, and no annotations, the description is complete enough for correct invocation. It covers purpose, timing, locale matching, authentication, and error behavior; return-value details can be 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 already 100%, and the schema documents the language parameter, default, and need to match create_recipe. The description adds useful semantics: valid option ids are language-specific and differ between locales, which explains why the parameter matters.

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 a specific verb and resource: list valid option identifiers for creating a recipe. It enumerates the option categories and clearly scopes the tool to language-specific creation metadata, making it distinguishable from siblings such as list_recipe_filters or create_recipe.

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?

It gives an explicit usage rule: call this before create_recipe whenever setting complexity_id or category_ids. It also explains why those ids require this call and adds the prerequisite login step, leaving no ambiguity about when to use it.

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