Unofficial Monsieur Cuisine MCP

by githubllff

Overview Schema Source Related Servers Discussions Admin

Python

Local

Add Favorite Recipe

add_favorite_recipe

Adds a recipe to the logged-in user's favorites using its translationId; run the login command first to save a session.

Instructions

Add a recipe to the logged-in user's favorites (bookmarks).

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.

IMPORTANT: translation_id is the recipe's translationId field from a search_recipes/get_recipe result - NOT the numeric recipe id used by those same tools. Always call search_recipes or get_recipe first to look up the correct translationId for the recipe to add.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "translation_id": "<translation_id>"
    },
    "name": "add_favorite_recipe"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Locale for the response message, e.g. "pl-PL", "en-US".	en-US
`translation_id`	Yes	The `translationId` of the recipe to add, from a search_recipes/get_recipe result.

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/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 it discloses the auth/session requirement and the explicit failure mode. It does not say what happens on a duplicate add (idempotent vs error) or whether the operation is reversible, which are the remaining behavioral gaps for a bookmarking mutation.

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 prerequisites, then the critical ID warning. Every sentence carries signal, though the 'raises an error telling the user to do that' sentence partly restates the login instruction already given.

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 need no explanation, and the description covers auth, the lookup workflow, and ID semantics for this two-parameter tool. Only duplicate-add behavior and the effect on the recipe's favorite state are missing.

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 the baseline would be 3, but the description adds a genuinely important disambiguation: translation_id is the recipe's translationId from search results, NOT the numeric `id` those same tools return. The `language` parameter is left to the schema, which documents it adequately.

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 ('Add a recipe to the logged-in user's favorites (bookmarks)') and clarifies the scope is the logged-in user rather than a list. The inverse sibling remove_favorite_recipe is implicitly differentiated by the verb choice, so an agent can route correctly without opening either schema.

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 sequence: a saved login session must exist, otherwise the tool raises an error naming the fix. It also states the mandatory lookup step ('Always call search_recipes or get_recipe first'), which is exactly the when-to-use guidance an agent needs.

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