Skip to main content
Glama
evcraddock

mealplan-mcp

by evcraddock
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MEALPLANPATHYesPath to the directory where meal plans are stored

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
add_ignored_ingredientB

Add an ingredient to the ignored ingredients list.

Args:
    ingredient: The name of the ingredient to ignore

Returns:
    A dictionary with a confirmation message
get_ignored_ingredientsA

Get the list of ignored ingredients.

Returns:
    A sorted list of ingredient names to be ignored in grocery lists
store_dishC

Store a dish and return a confirmation.

Args:
    dish_data: Dictionary containing dish data

Returns:
    Dictionary with a confirmation message including the path where the dish was stored
list_dishesC

List all dishes.

Returns:
    List of dish objects converted to dictionaries
generate_grocery_listB

Generate a grocery list for a specified date range.

Args:
    date_range: Dictionary containing start and end dates in format YYYY-MM-DD
        - start: Start date (required)
        - end: End date (required)

Returns:
    Dictionary with the path to the generated grocery list
create_mealplanB

Create a meal plan entry with the specified parameters and save it to a file.

Args:
    meal_plan: A meal plan object containing:
        - date: The date for the meal plan
        - meal_type: The type of meal (breakfast, lunch, dinner, snack)
        - title: The title of the meal
        - cook: The person who will cook the meal
        - dishes: List of dishes to be prepared

Returns:
    str: A summary of the meal plan and the path where it was saved
list_mealplans_by_date_rangeA

List meal plans within a specified date range.

Args:
    date_range: Dictionary containing start and end dates in format YYYY-MM-DD
        - start: Start date (required)
        - end: End date (required)

Returns:
    JSON string containing array of meal plan objects with:
    - title: Meal title (cleaned)
    - date: Date in YYYY-MM-DD format
    - meal_type: Type of meal (breakfast, lunch, dinner, snack)
    - cook: Person cooking the meal
    - dishes: Array of dish names
export_mealplans_to_pdfA

Export meal plans within a specified date range to a PDF file.

Args:
    date_range: Dictionary containing start and end dates in format YYYY-MM-DD
        - start: Start date (required)
        - end: End date (required)

Returns:
    JSON string containing either:
    - Success: {"ok": "path/to/generated.pdf"}
    - Error: {"error": "error_type", "message": "error_description"}

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct action and resource: adding/listing ignored ingredients, storing/listing dishes, creating/listing meal plans, generating grocery lists, and exporting PDFs. No two tools have overlapping purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_ignored_ingredient, list_dishes, generate_grocery_list). There are no style mix-ups or ambiguous verbs.

Tool Count5/5

Eight tools is well-scoped for a meal planning server. The set covers the main operations without being too sparse or bloated, making it easy for agents to navigate.

Completeness2/5

The tool set lacks update and delete operations for all resources (dishes, meal plans, grocery lists, ignored ingredients), and there is no way to retrieve a single dish or meal plan by ID. These gaps significantly limit the agent's ability to manage meal data fully.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources