Skip to main content
Glama
Symfomany

Recettes MCP Server

by Symfomany

scrape_christmas_recipes

Extract Christmas recipe titles from Marmiton.org to gather culinary inspiration for holiday meal planning.

Instructions

Scrapes Christmas recipe titles from Marmiton.org.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:350-360 (handler)
    The asynchronous handler function that implements the scraping logic for Christmas recipes from Marmiton.org using requests and BeautifulSoup, parsing titles from links containing '/recettes/recette_'.
    async def scrape_christmsas_recipes() -> List[str]:
        """Scrape les titres des recettes de Noël depuis Marmiton.org."""
        url = "https://www.marmiton.org/recettes/recherche.aspx?aqt=noël"
        response = requests.get(url)
        soup = BeautifulSoup(response.content, 'html.parser')
        recipes = []
        for item in soup.find_all('a', href=lambda x: x and '/recettes/recette_' in x):
            title = item.text.strip()
            if title:
                recipes.append(title)
        return recipes[:10]  # Limiter à 10 pour l'exemple
  • main.py:346-349 (registration)
    The @mcp.tool decorator that registers the 'scrape_christmas_recipes' tool with its name and description.
    @mcp.tool(
        name="scrape_christmas_recipes",
        description="Scrapes Christmas recipe titles from Marmiton.org.",
    )
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions scraping but doesn't cover critical aspects like rate limits, authentication needs, data format, or potential side effects (e.g., web scraping implications). This leaves significant gaps in understanding the tool's behavior.

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 directly states the tool's function without any wasted words. It is front-loaded and appropriately sized for a simple tool, making it highly concise and well-structured.

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, output schema exists), the description is adequate but minimal. It covers the basic purpose but lacks details on behavioral traits and usage context, which are important even for simple tools, especially with no annotations to fill those gaps.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, aligning with the schema's completeness, which justifies a baseline score of 4 for this dimension.

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 action ('scrapes') and resource ('Christmas recipe titles from Marmiton.org'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_christmas_recipes', which might offer similar functionality through different means.

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 such as 'list_christmas_recipes' or 'get_random_recipe'. The description lacks context about prerequisites, timing, or exclusions, leaving the agent without usage direction.

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