Skip to main content
Glama
Symfomany

Recettes MCP Server

by Symfomany

create_shopping_list

Generate a shopping list for any recipe by providing the recipe name, helping you prepare ingredients before cooking.

Instructions

Creates a shopping list for a recipe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recipe_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:218-223 (handler)
    The asynchronous handler function that executes the core logic of the 'create_shopping_list' tool by searching for a matching recipe and returning its ingredients.
    async def create_shopping_list(recipe_name: str) -> Dict:
        """Crée une liste de courses pour une recette."""
        for recipe in christmas_recipes():
            if recipe.name.lower() == recipe_name.lower():
                return {"recipe": recipe.name, "ingredients": recipe.ingredients}
        return {"error": "Recette non trouvée."}
  • main.py:214-217 (registration)
    The @mcp.tool decorator that registers the 'create_shopping_list' tool with its name and description.
    @mcp.tool(
        name="create_shopping_list",
        description="Creates a shopping list for a recipe.",
    )
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. 'Creates' implies a write operation, but the description doesn't specify permissions, side effects, error handling, or output format. It lacks details on what 'creates' entails (e.g., saves to a database, generates a list format) and behavioral traits like rate limits or idempotency, leaving significant gaps for a mutation tool.

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 purpose without unnecessary words. It is front-loaded with the core action ('Creates') and resource, making it easy to parse. Every part of the sentence contributes to understanding, achieving optimal conciseness for the given information.

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 one parameter with 0% schema coverage and an output schema exists, the description is minimally adequate. It covers the basic purpose but lacks details on usage guidelines, behavioral transparency, and parameter semantics. The output schema mitigates the need to explain return values, but for a creation tool with no annotations, more context on behavior and usage would improve completeness.

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 mentions 'for a recipe', which aligns with the single parameter 'recipe_name' in the input schema. However, schema description coverage is 0%, so the schema provides no parameter details. The description adds minimal semantic context by linking the parameter to recipe creation but doesn't explain the parameter's role, format, or constraints beyond this basic association, partially compensating for the low coverage.

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 ('Creates') and resource ('shopping list'), and specifies the context ('for a recipe'). It distinguishes from siblings like 'list_ingredients' or 'scale_recipe' by focusing on creation rather than listing or modification. However, it doesn't explicitly differentiate from all siblings, such as 'generate_recipe_from_ingredients', which might also involve shopping list creation indirectly.

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 prerequisites (e.g., needing a recipe first), exclusions, or comparisons to siblings like 'list_ingredients' or 'search_by_ingredient'. The context 'for a recipe' implies usage but lacks explicit when/when-not instructions or named alternatives.

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