Skip to main content
Glama
Symfomany

Recettes MCP Server

by Symfomany

list_christmas_recipes

Get a collection of Christmas recipes for holiday cooking and meal planning. This tool provides festive dish ideas to help you prepare seasonal meals.

Instructions

Returns a list of all Christmas recipes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:149-152 (handler)
    The main handler function for the 'list_christmas_recipes' tool. It calls the 'christmas_recipes' resource and converts the Recipe models to dictionaries for return.
    async def list_christmas_recipes() -> List[Dict]:
        """Retourne la liste de toutes les recettes de Noël."""
        return [recipe.model_dump() for recipe in christmas_recipes()]
  • main.py:50-57 (schema)
    Pydantic BaseModel defining the schema for Recipe objects, which structure the output data of the tool.
    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
  • main.py:145-148 (registration)
    The @mcp.tool decorator that registers the 'list_christmas_recipes' tool with its name and description.
    @mcp.tool(
        name="list_christmas_recipes",
        description="Returns a list of all Christmas recipes.",
    )
  • The 'christmas_recipes' resource function that provides the hardcoded list of Christmas recipes used by the tool handler. (Excerpt shows structure; full list includes 3 recipes.)
    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. It states the tool returns a list but doesn't describe the return format, pagination, sorting, or any limitations (e.g., number of recipes, freshness of data). For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 with zero waste. It's front-loaded with the core action ('Returns a list') and resource ('all Christmas recipes'), making it easy to scan. Every word earns its place without redundancy.

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's simplicity (0 parameters, read-only operation) and the presence of an output schema (which should document return values), the description is minimally adequate. However, it lacks context about the list's scope (e.g., all recipes ever, current database), which could be important for usage. With no annotations, it should ideally mention that it's a safe read operation.

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 0 parameters, and schema description coverage is 100% (though empty). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for zero-parameter tools. It appropriately doesn't discuss inputs beyond confirming no filtering or arguments are required.

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 purpose with a specific verb ('Returns') and resource ('list of all Christmas recipes'). It distinguishes from siblings like 'get_random_recipe' or 'search_by_ingredient' by implying a comprehensive, unfiltered list. However, it doesn't explicitly differentiate from 'scrape_christmas_recipes' which might have overlapping functionality.

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. It doesn't mention when to choose this over 'get_random_recipe' for a single recipe, 'search_by_ingredient' for filtered results, or 'scrape_christmas_recipes' which might be a data source. There's no context about prerequisites or exclusions.

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