Skip to main content
Glama
Symfomany

Recettes MCP Server

by Symfomany

get_recipe_by_index

Retrieve a specific Christmas recipe using its numerical index to access culinary content from recipe databases.

Instructions

Retrieves a Christmas recipe by its index (1-based).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:369-374 (handler)
    The asynchronous handler function that implements the logic for retrieving a specific Christmas recipe by its 1-based index from the predefined list, returning the recipe as a dictionary or an error if index is invalid.
    async def get_recipe_by_index(index: int) -> Dict:
        """Récupère une recette de Noël par son index (1-based)."""
        recipes = christmas_recipes()
        if 1 <= index <= len(recipes):
            return recipes[index - 1].model_dump()
        return {"error": "Index de recette invalide."}
  • main.py:365-368 (registration)
    The @mcp.tool decorator that registers the get_recipe_by_index tool with its name and description.
    @mcp.tool(
        name="get_recipe_by_index",
        description="Retrieves a Christmas recipe by its index (1-based).",
    )
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but only states it retrieves by index without disclosing behavioral traits such as error handling for invalid indices, response format, or any constraints like rate limits. It mentions the index is 1-based, which is useful but insufficient for a tool with no annotation coverage.

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, clearly front-loaded with the core action. Every part earns its place by specifying key details like 'Christmas recipe' and '1-based'.

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 simplicity (1 parameter) and the presence of an output schema, the description is adequate but lacks depth. It doesn't explain what a 'Christmas recipe' entails or potential errors, relying on the output schema for return values, which is acceptable but leaves gaps in behavioral context.

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

Parameters4/5

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

The description adds meaning beyond the input schema by specifying that the index is 1-based, which is not covered in the schema (0% description coverage). Since there's only one parameter, this compensates well, though it doesn't detail range or validation.

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 verb ('retrieves') and resource ('Christmas recipe'), specifying it's by index and noting it's 1-based. It distinguishes from siblings like 'get_random_recipe' and 'list_christmas_recipes' by focusing on index-based retrieval, though it doesn't explicitly contrast them.

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 guidance on when to use this tool versus alternatives like 'get_random_recipe' or 'list_christmas_recipes' is provided. The description implies usage when you have a specific index, but lacks explicit context, prerequisites, or exclusions.

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