Skip to main content
Glama
Symfomany

Recettes MCP Server

by Symfomany

invent_recipe

Generate culinary recipes from available ingredients, providing structured cooking instructions and serving sizes for meal planning.

Instructions

Invents a recipe from ingredients (structured format).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ingredientsYes
servingsNo

Implementation Reference

  • main.py:273-284 (handler)
    The main handler function that executes the tool logic for 'invent_recipe', taking ingredients and servings, and returning a simple recipe dictionary.
    async def invent_recipe(ingredients: list[str], servings: int = 4) -> dict:
        """Invente une recette à partir des ingrédients et du nombre de personnes."""
        logger.info("invent_recipe called with ingredients=%s, servings=%s", ingredients, servings)
    
        # ta logique
        recipe = {
            "title": "Entrée de fête au foie gras et fruits",
            "ingredients": ingredients,
            "servings": servings,
        }
        logger.info("invent_recipe returning recipe=%s", recipe)
        return recipe
  • main.py:269-272 (registration)
    The decorator that registers the 'invent_recipe' tool with MCP, specifying its name and description.
    @mcp.tool(
        name="invent_recipe",
        description="Invents a recipe from ingredients (structured format).",
    )
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'invents' (implying creative generation) and 'structured format', but fails to disclose critical behavioral traits such as whether this is a read-only or mutating operation, potential rate limits, authentication needs, or what the output looks like (e.g., recipe details, steps, or just a name). This leaves significant gaps for a tool that likely involves AI generation.

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?

The description is concise with a single sentence, front-loading the core action. However, the parenthetical '(structured format)' feels tacked on and could be integrated more smoothly, and the brevity comes at the cost of completeness, as noted in other dimensions.

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

Completeness2/5

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

Given the complexity (creative generation tool with no annotations, 0% schema coverage, and no output schema), the description is incomplete. It doesn't explain the tool's behavior, output format, or how it differs from siblings, making it inadequate for an agent to use effectively without additional context or trial-and-error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It only vaguely references 'ingredients (structured format)', which partially explains the 'ingredients' parameter but doesn't clarify the structure (e.g., list of strings, quantities, or categories) or mention the 'servings' parameter at all. This adds minimal meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Invents a recipe from ingredients (structured format)' clearly states the action ('invents') and resource ('recipe'), but it's vague about what 'invents' entails (e.g., creative generation vs. retrieval) and doesn't distinguish it from siblings like 'generate_recipe_from_ingredients' or 'invent_magical_recipe'. The parenthetical '(structured format)' adds some specificity but is ambiguous.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. With siblings like 'generate_recipe_from_ingredients' and 'invent_magical_recipe', the description lacks any context about differences (e.g., mundane vs. magical recipes, input formats, or output styles), leaving the agent to guess based on tool names alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Symfomany/mcp-tuto'

If you have feedback or need assistance with the MCP directory API, please join our Discord server