Skip to main content
Glama
mhlavac

loewen-menu-mcp

by mhlavac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PROFILESYesCredentials formatted as 'child1:CUSTOMER_ID:PASSWORD' or comma-separated for multiple children: 'child1:CUSTOMER_ID:PASSWORD,child2:CUSTOMER_ID2:PASSWORD2'

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
list_profilesA

List all configured profiles (children).

Returns:
    Names of available profiles that can be used with other tools.
get_weekly_menuA

Get the weekly meal plan for a given week.

Args:
    profile: Profile name (e.g. "child1"). Optional if only one profile is configured.
    year: Year (defaults to current year)
    week: Calendar week number (defaults to current week)

Returns:
    Formatted menu for the week with all available meals grouped by date
    and menu line (GS 1, GS 2, GS 3).
get_order_historyA

Get past order history.

Args:
    profile: Profile name (e.g. "child1"). Optional if only one profile is configured.
    days_back: How many days back to look (default 60)
    search: Optional search text to filter orders

Returns:
    List of past orders with dates, descriptions, and quantities.
get_cart_statusA

Check the current shopping cart status and balance.

Args:
    profile: Profile name (e.g. "child1"). Optional if only one profile is configured.

Returns:
    Cart item count, total price, and credit balance.
add_to_cartA

Add a meal to the shopping cart. Does NOT place the order yet.

You MUST call confirm_order afterwards to finalize the order.

Note: Orders must be placed at least 1 day before the delivery date.

Args:
    serve_date: Delivery date in YYYY-MM-DD format (e.g. "2026-02-25")
    menu_line_id: Menu line ID (8=GS1, 9=GS2, 10=GS3 — shown in get_weekly_menu output)
    profile: Profile name (e.g. "child1"). Optional if only one profile is configured.
    quantity: Number of portions (default 1, usually max 2)
    menu_group_id: Menu group ID (default "2", shown in get_weekly_menu output)

Returns:
    Cart status. Remember to call confirm_order to finalize.
remove_mealB

Remove a meal from the shopping cart (set quantity to 0).

Args:
    serve_date: Delivery date in YYYY-MM-DD format
    menu_line_id: Menu line ID (8=GS1, 9=GS2, 10=GS3)
    profile: Profile name (e.g. "child1"). Optional if only one profile is configured.
    menu_group_id: Menu group ID (default "2")

Returns:
    Confirmation that the meal was removed from cart.
confirm_orderA

Confirm and finalize all items currently in the shopping cart.

This submits the order. Items must first be added with add_to_cart.
Call get_cart_status first to verify what will be ordered.

Args:
    profile: Profile name (e.g. "child1"). Optional if only one profile is configured.

Returns:
    Confirmation message from the server.

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

A4.1/5.0

Scored across 7 tools

Disambiguation5/5

Each tool addresses a distinct part of the workflow: profiles, menu browsing, cart management, ordering, and history. There is no meaningful overlap between tools, and an agent can confidently select the correct one from its name and description alone.

Naming Consistency4/5

Tool names are predominantly verb_noun in snake_case, such as list_profiles, get_weekly_menu, and confirm_order. Minor inconsistency exists between add_to_cart and remove_meal, but the overall pattern is clear and predictable.

Tool Count5/5

Seven tools is well-scoped for a school-menu ordering server. Each tool covers a necessary step in the workflow without redundancy or unnecessary bloat.

Completeness5/5

The tool surface covers the full ordering lifecycle: browse the menu, add items, remove items, inspect the cart, confirm the order, and review past orders. No obvious gaps exist for the stated purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources