Skip to main content
Glama
Symfomany

Recettes MCP Server

by Symfomany

suggest_christmas_menu

Generate a complete Christmas menu with starter, main course, and dessert suggestions for holiday meal planning.

Instructions

Suggests a complete Christmas menu (starter, main course, dessert).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:177-188 (handler)
    The main handler function for the 'suggest_christmas_menu' tool. It filters Christmas recipes by category and randomly selects one from each (Entrée, Plat principal, Dessert) to form a menu.
    async def suggest_christmas_menu() -> Dict[str, Dict]:
        """Suggère un menu de Noël complet (entrée, plat, dessert)."""
        recipes = christmas_recipes()
        entrees = [r for r in recipes if r.category == "Entrée"]
        plats = [r for r in recipes if r.category == "Plat principal"]
        desserts = [r for r in recipes if r.category == "Dessert"]
    
        return {
            "entree": random.choice(entrees).model_dump() if entrees else None,
            "plat_principal": random.choice(plats).model_dump() if plats else None,
            "dessert": random.choice(desserts).model_dump() if desserts else None,
        }
  • main.py:173-176 (registration)
    MCP tool registration decorator defining the name and description of the 'suggest_christmas_menu' tool.
    @mcp.tool(
        name="suggest_christmas_menu",
        description="Suggests a complete Christmas menu (starter, main course, dessert).",
    )
  • main.py:50-57 (schema)
    Pydantic model used for defining the structure of individual recipes in the Christmas menu output.
    class Recipe(BaseModel):
        name: str
        category: str  # "Entrée", "Plat principal", "Dessert"
        servings: int
        ingredients: Dict[str, str]  # e.g., {"chocolat noir": "200g"}
        instructions: List[str]
        wine_pairing: Optional[str] = None
  • Helper function providing the list of hardcoded Christmas recipes used by the tool to select menu items.
    def christmas_recipes() -> List[Recipe]:
        """Liste de recettes de Noël."""
        return [
            Recipe(
                name="Dinde de Noël",
                category="Plat principal",
                servings=8,
                ingredients={"dinde": "1", "marrons": "500g", "beurre": "100g", "sel": "1 pincée", "poivre": "1 pincée"},
                instructions=[
                    "Préchauffer le four à 180°C.",
                    "Farcir la dinde avec les marrons.",
                    "Badigeonner de beurre, saler et poivrer.",
                    "Enfourner pour 3 heures.",
                ],
                wine_pairing="Bourgogne rouge",
            ),
            Recipe(
                name="Bûche de Noël",
                category="Dessert",
                servings=6,
                ingredients={"chocolat noir": "200g", "beurre": "100g", "sucre": "150g", "oeufs": "4", "farine": "50g"},
                instructions=[
                    "Faire fondre le chocolat avec le beurre.",
                    "Ajouter le sucre, les oeufs et la farine.",
                    "Verser sur une plaque et cuire 10 minutes.",
                    "Rouler la bûche et la laisser refroidir.",
                ],
                wine_pairing="Champagne",
            ),
            Recipe(
                name="Saumon fumé sur blinis",
                category="Entrée",
                servings=4,
                ingredients={"saumon fumé": "4 tranches", "blinis": "8", "crème fraîche": "100g", "ciboulette": "1 botte"},
                instructions=[
                    "Tartiner les blinis de crème fraîche.",
                    "Ajouter une tranche de saumon fumé.",
                    "Ciseler la ciboulette et en parsemer les blinis.",
                ],
                wine_pairing="Sancerre",
            ),
        ]
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 of behavioral disclosure. While 'suggests' implies a read-only operation, it doesn't clarify whether this is deterministic or random, if it requires user preferences, how comprehensive the suggestions are, or what the output format looks like. The description lacks essential behavioral context for a tool with no annotation coverage.

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 description is a single, efficient sentence that states the tool's purpose without any wasted words. It's appropriately sized for a zero-parameter tool and front-loads the essential information. Every word earns its place.

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

Completeness3/5

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

Given the tool has zero parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, for a suggestion tool with no annotations, it should ideally provide more context about how suggestions are generated or what the output contains. The existence of an output schema reduces the need to describe return values, but behavioral transparency remains lacking.

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?

The tool has zero parameters, and schema description coverage is 100%, so there are no parameters to document. The description appropriately doesn't mention any parameters, which aligns perfectly with the schema. A baseline of 4 is appropriate since no parameter information is needed.

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?

The description clearly states the tool's function: 'Suggests a complete Christmas menu' with specific components (starter, main course, dessert). It uses a specific verb ('suggests') and resource ('Christmas menu'), but doesn't explicitly differentiate from sibling tools like 'list_christmas_recipes' or 'invent_recipe', which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'list_christmas_recipes', 'invent_recipe', and 'suggest_wine_pairing', there's no indication of when this menu suggestion tool is preferred over those options or any prerequisites for its use.

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