Skip to main content
Glama
Symfomany

Recettes MCP Server

by Symfomany

suggest_wine_pairing

Find wine recommendations for your recipes to enhance culinary experiences and complement flavors.

Instructions

Suggests a wine pairing for a recipe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recipe_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:229-234 (handler)
    The asynchronous handler function that implements the logic for suggesting a wine pairing based on the provided recipe name by searching through Christmas recipes.
    async def suggest_wine_pairing(recipe_name: str) -> Dict:
        """Suggère un accord mets-vin pour une recette."""
        for recipe in christmas_recipes():
            if recipe.name.lower() == recipe_name.lower():
                return {"recipe": recipe.name, "wine_pairing": recipe.wine_pairing}
        return {"error": "Recette non trouvée."}
  • main.py:225-228 (registration)
    The @mcp.tool decorator registration for the suggest_wine_pairing tool, specifying its name and description.
    @mcp.tool(
        name="suggest_wine_pairing",
        description="Suggests a wine pairing for a recipe.",
    )
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 but only states the basic action without details on how it works. It doesn't mention if this is a read-only operation, if it requires external data, potential limitations (e.g., based on a database), or what the output entails, which is insufficient for a tool with no annotation support.

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 extremely concise—a single sentence that directly states the tool's function without any fluff. It's front-loaded and wastes no words, making it efficient for quick understanding, though this brevity contributes to gaps in other dimensions.

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 low complexity (1 parameter) and the presence of an output schema, the description is minimally adequate but incomplete. It covers the basic purpose but lacks details on usage, behavior, and parameter context, which are needed for full agent guidance, especially with no annotations to fill gaps.

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?

The description implies the need for a recipe but doesn't add meaning beyond the input schema, which has 0% description coverage for the single parameter 'recipe_name'. Since schema coverage is low, the description should compensate by explaining parameter expectations (e.g., format, examples), but it doesn't, resulting in a baseline score due to the minimal parameter count.

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 ('suggests') and resource ('wine pairing for a recipe'), making it immediately understandable. However, it doesn't distinguish this tool from potential sibling tools like 'suggest_christmas_menu', which might also involve pairing suggestions, leaving room for ambiguity in a broader context.

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, such as 'suggest_christmas_menu' or other recipe-related tools. It lacks context about prerequisites, like whether a recipe must be specified or if it works with any recipe type, leaving the agent to infer usage without explicit 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