Skip to main content
Glama
Symfomany

Recettes MCP Server

by Symfomany

elicit_user_needs

Create personalized recipes by specifying available ingredients, cooking utensils, and time constraints to match your culinary needs.

Instructions

Helps the user create a recipe based on their needs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ingredientsNo
utensilsNo
timeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:316-319 (registration)
    Registration of the 'elicit_user_needs' tool using the @mcp.tool decorator.
    @mcp.tool(
        name="elicit_user_needs",
        description="Helps the user create a recipe based on their needs.",
    )
  • main.py:320-330 (handler)
    Implementation of the tool handler function, which returns the provided input parameters (ingredients, utensils, time).
    async def elicit_user_needs(
        ingredients: Optional[List[str]] = None,
        utensils: Optional[List[str]] = None,
        time: Optional[int] = None,
    ) -> Dict[str, object]:
        """Aides l'utilisateur a créér une recette à partir de ses besoins"""
        return {
            "ingredients": ingredients,
            "utensils": utensils,
            "time": time,
        }
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 'Helps the user create a recipe,' which suggests a generative or interactive process, but doesn't detail how it works (e.g., whether it prompts for input, returns structured data, or has side effects). This is insufficient for a tool with potential complexity in eliciting needs.

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 that states the tool's purpose without unnecessary words. It's front-loaded and easy to parse, though it could be more informative. The brevity is appropriate but under-specified rather than concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 3 parameters with 0% schema coverage, no annotations, and an output schema (which isn't described), the description is incomplete. It doesn't address input semantics, behavioral traits, or how it relates to sibling tools, making it inadequate for effective tool selection and use in a complex environment.

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?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It doesn't mention any parameters (ingredients, utensils, time) or explain their roles in eliciting needs. This leaves the input schema's purpose unclear, failing to add meaning beyond the bare 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 'Helps the user create a recipe based on their needs,' which provides a general purpose (verb: 'create a recipe') but is vague about what 'elicit_user_needs' specifically entails compared to siblings like 'generate_recipe_from_ingredients' or 'invent_recipe.' It doesn't clearly differentiate itself, making it ambiguous whether it's for gathering input or generating recipes directly.

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 explicit guidance on when to use this tool versus alternatives is provided. The description implies it's for recipe creation based on user needs, but it doesn't specify contexts, prerequisites, or exclusions, such as whether it's for initial brainstorming versus using existing ingredients. With many sibling tools for recipe generation, this lack of differentiation leaves usage unclear.

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