Skip to main content
Glama
Symfomany

Recettes MCP Server

by Symfomany

list_ingredients

Get a list of ingredients organized by cooking style to help plan meals and manage culinary resources.

Instructions

Returns a list of ingredients based on a simple style.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNobasics

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:257-260 (registration)
    Registration of the 'list_ingredients' tool using @mcp.tool decorator.
    @mcp.tool(
        name="list_ingredients",
        description="Returns a list of ingredients based on a simple style.",
    )
  • main.py:261-268 (handler)
    Handler function that implements the logic for listing ingredients based on style, returning lists of strings.
    async def list_ingredients(style: str = "basics") -> List[str]:
        """Retourne une liste d'ingrédients selon un style simple."""
        if style == "basics":
            return default_ingredients()
        if style == "fridge":
            return ["oeufs", "fromage râpé", "lait", "beurre", "restes de légumes", "riz"]
        return ["pain", "tomate", "mozzarella", "basilic", "huile d'olive"]
  • main.py:62-77 (helper)
    Helper resource function 'default_ingredients' called by the handler when style='basics', providing a default list of ingredients.
    @mcp.resource(
        "recipes://ingredients/default",
        description="Default ingredients list.",
    )
    def default_ingredients() -> List[str]:
        """Liste d'ingrédients par défaut."""
        return [
            "pâtes",
            "tomates concassées",
            "ail",
            "oignon",
            "huile d'olive",
            "sel",
            "poivre",
        ]
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 mentions returning a list but doesn't specify format, pagination, or any constraints like rate limits or authentication needs. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core purpose, though it could be more structured by explicitly separating purpose from parameter context.

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 an output schema, the description doesn't need to explain return values. However, with no annotations, 1 parameter at 0% coverage, and multiple sibling tools, the description is incomplete—it lacks usage context, parameter details, and behavioral traits, making it only minimally adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 1 parameter with 0% description coverage, so the description must compensate. It mentions 'based on a simple style', which loosely relates to the 'style' parameter, but doesn't explain what 'style' means, possible values, or how it affects the output. This adds minimal value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'Returns a list of ingredients', which provides a basic verb+resource combination. However, it's vague about what 'based on a simple style' means, and it doesn't distinguish this tool from sibling tools like 'list_magical_ingredients' or 'search_by_ingredient', leaving ambiguity about its specific scope.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, and with multiple sibling tools related to ingredients and recipes, the lack of differentiation makes it unclear when this tool is the appropriate choice.

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