Mon Batch Cooking

Chercher des recettes de batch cooking

chercher_recettes

Read-onlyIdempotent

Cherche parmi les recettes de batch cooking publiées (plusieurs centaines, en français). Renvoie pour chacune son identifiant, son temps, ses calories, ses portions et le lien de sa page.

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

Input Schema

Name	Required	Description
`type`	No	Type de recette (facultatif)
`texte`	No	Mots du titre ou des ingrédients, ex. « poulet curry », « lentilles », « soupe » (facultatif)
`nombre`	No	Nombre de résultats (8 par défaut, 20 au plus)
`regime`	No	Régime alimentaire compatible (facultatif)
`kcalMax`	No	Calories maximales par portion (facultatif)
`appareil`	No	Recettes pour air fryer ou robot cuiseur type Thermomix (facultatif)
`sansGluten`	No	Seulement les recettes sans gluten (facultatif)
`tempsMaxMin`	No	Temps total maximal en minutes (facultatif)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine value beyond them by enumerating the fields returned per hit (identifiant, temps, calories, portions, lien de page) and by disclosing the bounded, French-language corpus — which corroborates openWorldHint=false. It stops short of describing result ordering or the effect of the "nombre" limit.

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?

Two sentences, no filler: the first establishes what is searched and over what corpus, the second what comes back. Front-loaded and every clause earns its place.

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?

For an 8-parameter, all-optional search with no output schema, the description adequately covers both the query surface (catalogue scope) and the return shape. The main remaining gap is the absence of any guidance on ranking/ordering of results or on how it relates to the other recipe-lookup siblings.

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% across all 8 optional parameters, so the schema already carries the parameter semantics and the baseline is 3. The description's mention of "temps" and "calories" refers to returned fields, not to the tempsMaxMin/kcalMax filters, so it contributes nothing incremental on parameters.

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 ("Cherche") and resource ("recettes de batch cooking publiées"), and even bounds the corpus ("plusieurs centaines, en français"). It does not, however, differentiate itself from the sibling "recettes_avec", which by name also appears to look up recipes — so an agent could not tell them apart from the description alone.

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

Usage Guidelines3/5

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

The description implies the usage context (searching the published recipe catalogue with filters) but never states when to prefer this over "recettes_avec" or "idees_session", nor any exclusions or prerequisites. Usage is inferable from the purpose, not spelled out.

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

All Mon Batch Cooking tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?