Skip to main content
Glama
Symfomany

Recettes MCP Server

by Symfomany

list_magical_ingredients

Retrieve magical ingredients filtered by style to support recipe creation and culinary management within the Recettes MCP Server.

Instructions

Returns a list of magical ingredients by style.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNobasics

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:338-344 (handler)
    The main handler function implementing the logic to return lists of magical ingredients based on the provided style ('basics', 'dark', or default).
    async def list_magical_ingredients(style: str = "basics") -> List[str]:
        """Retourne une liste d'ingrédients magiques selon un style."""
        if style == "basics":
            return ["poudre de licorne", "ailes de fée", "potion d'élixir", "feuilles de mandragore", "cristaux de lune"]
        if style == "dark":
            return ["sang de dragon", "œil de troll", "racine de belladone", "poussière de vampire", "larmes de sirène"]
        return ["étoiles filantes", "nectar d'arc-en-ciel", "plumes de phénix", "ambre magique", "eau de source enchantée"]
  • main.py:334-337 (registration)
    The @mcp.tool decorator that registers the tool with the specified name and description.
    @mcp.tool(
        name="list_magical_ingredients",
        description="Returns a list of magical ingredients by style.",
    )
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, implying a read-only operation, but lacks details on permissions, rate limits, pagination, or error handling. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 no wasted words. It is front-loaded with the core purpose and includes the key parameter constraint, making it easy to parse and understand quickly.

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 (one optional parameter) and the presence of an output schema, the description is minimally complete. However, with no annotations and multiple sibling tools, it lacks context on behavioral traits and usage differentiation, leaving gaps for the agent to navigate.

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 adds minimal semantics beyond the input schema: it mentions the 'style' parameter but provides no details on allowed values or examples. With 0% schema description coverage and only one parameter, the description partially compensates but doesn't fully clarify usage, resulting in an adequate baseline score.

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 magical ingredients'), and it includes a key parameter constraint ('by style'). However, it doesn't explicitly differentiate from sibling tools like 'list_ingredients' or 'search_by_ingredient', which could cause confusion in selection.

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. There are multiple sibling tools related to ingredients and recipes (e.g., 'list_ingredients', 'search_by_ingredient'), but the description offers no context on use cases, prerequisites, or exclusions, leaving the agent to infer usage.

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