Unofficial Monsieur Cuisine MCP

by githubllff

Overview Schema Source Related Servers Discussions Admin

Python

Local

List Favorite Recipes

list_favorite_recipes

Retrieves a logged-in user's bookmarked recipes with full details and supports paging, sorting, and language selection.

Instructions

List the logged-in user's favorite (bookmarked) recipes, with full recipe details for each one.

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

Each result's top-level translationId field is what remove_favorite_recipe expects - not the nested recipe's id field.

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_favorite_recipes"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	1-based page number.
`language`	No	Result language/locale, e.g. "pl-PL", "en-US".	en-US
`page_size`	No	Number of favorites per page.
`sort_field`	No	Field to sort by, e.g. "date".	date
`sort_direction`	No	"ASC" or "DESC".	DESC

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the authentication requirement, the exact remedy command, and the error behavior when no session exists. It also pre-empts a likely mistake by warning that the top-level `translationId` is the identifier remove_favorite_recipe expects, not the nested recipe `id`. It stops short of noting payload size or how pagination terminates.

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 capability is front-loaded in the first sentence, followed by the prerequisite and then the one gotcha an agent is most likely to trip on. Every sentence carries actionable information, and the paragraph breaks map cleanly onto purpose, precondition, and output caveat.

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

Completeness4/5

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

An output schema exists, so return values needn't be enumerated, and the description wisely spends its budget on the auth requirement and the identifier caveat instead. For a five-parameter, paginated list tool the only remaining ambiguity is how to page through the full set of favorites, which is left unstated.

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 description coverage is 100%, so page, language, page_size, sort_field and sort_direction are already documented in structured form and the 3 baseline applies. The description adds no syntax or constraint detail beyond the schema; its extra meaning concerns the return payload's `translationId` rather than any input parameter.

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 (List) and resource ('the logged-in user's favorite (bookmarked) recipes') plus the fact that full recipe details are returned, so the agent knows exactly what comes back. It does not, however, distinguish itself from the similarly-scoped sibling list_my_recipes or explain how it relates to search_recipes, leaving the agent to infer the difference.

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?

Gives a concrete prerequisite (a saved login session created via `uv run monsieur-cuisine-mcp-login`) and states the failure mode if it is absent, which is real usage guidance. It also implies a downstream pairing with remove_favorite_recipe via the `translationId` note. What it lacks is any explicit statement of when to prefer this over list_my_recipes or search_recipes.

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