Unofficial Monsieur Cuisine MCP

Overview Schema Source Related Servers Discussions Admin

Search Ingredients

search_ingredients

Find exact Monsieur Cuisine ingredients and their systemIngredientId for recipe creation, avoiding first-match name resolution.

Instructions

Search the Monsieur Cuisine ingredient database, returning matching ingredients with their systemIngredientId.

Use this to find the system_ingredient_id for an ingredient before passing it to create_recipe, when you want to guarantee the exact database ingredient rather than relying on create_recipe's automatic first-match resolution of a plain name.

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

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": {
      "query": "<query>"
    },
    "name": "search_ingredients"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No	Maximum number of matches to return.
`query`	Yes	Ingredient term to search for (e.g. "flour"). Language-specific.
`language`	No	Locale to search in, e.g. "pl-PL", "en-US".	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.3/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 does well: it discloses the saved-login prerequisite and the exact failure mode (raises an error instructing the user to log in). It does not describe how results are ordered or what happens on zero matches, which are the remaining behavioral unknowns.

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 the action and return value, then the routing rule, then the prerequisite — a sensible order. Slightly padded by the second paragraph's restatement of create_recipe's resolution behavior, but nothing is wasted.

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 auth prerequisite plus failure behavior are covered. The only gap is empty-result handling, which is minor for a search tool.

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 coverage is 100%, so query, count, and language are fully documented in the schema, including the language-specific caveat. The description adds no syntax, matching-rule, or locale-fallback detail beyond that, so the baseline 3 applies.

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?

Specific verb + resource: searches the Monsieur Cuisine ingredient database and returns matches with their `systemIngredientId`. It distinguishes itself from the sibling search_recipes/create_recipe cluster by stating the returned identifier, so an agent knows exactly what it yields.

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 use case (resolve an id before passing to create_recipe) and an explicit when-not (avoid when create_recipe's automatic first-match name resolution is acceptable). The alternative path is named, not merely implied.

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