Skip to main content
Glama
jihopark

Grocery Logger MCP Server

by jihopark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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_grocery_itemsA

Bulk add grocery items to the database.

Use this tool to log one or more grocery purchases. Each item requires:

  • timestamp: When purchased (ISO format, e.g., "2025-01-10T14:30:00")

  • vendor: Store name (e.g., "Costco", "Whole Foods")

  • item_name: Product name WITHOUT quantity/weight (e.g., "Organic Bananas", "Frozen Cooked Mussel")

  • category: One of: produce, dairy, eggs, meat, seafood, bakery, deli, frozen, pantry, beverages, snacks, condiments, spices, household, personal_care, baby, pet, alcohol, other

  • price: Price paid (e.g., 3.99)

  • quantity: The numeric amount (e.g., 2.0, 340, 1.5)

  • unit: Unit of the quantity (e.g., "each", "lb", "oz", "g", "kg", "ml", "L", "bunch", "bag")

IMPORTANT: Parse quantity and unit from item descriptions. Examples:

  • "Frozen Cooked Mussel 340g" -> item_name: "Frozen Cooked Mussel", quantity: 340, unit: "g"

  • "2 lbs Ground Beef" -> item_name: "Ground Beef", quantity: 2, unit: "lb"

  • "Milk 1 gallon" -> item_name: "Milk", quantity: 1, unit: "gallon"

  • "3 Avocados" -> item_name: "Avocado", quantity: 3, unit: "each"

query_item_priceA

Get average price and price history for a grocery item.

Search for an item by name (partial match supported) and optionally filter by vendor. Returns average price and recent purchase history.

Args: item_name: Name to search for (e.g., "banana" matches "Organic Bananas") vendor: Optional vendor filter (e.g., "Costco") limit: Maximum history entries to return (default: 10)

list_items_by_categoryA

List all items in a category with their prices.

Get distinct items from a category (partial match supported). Optionally includes price statistics (min, max, average) per item.

Args: category: Category to search (e.g., "produce", "dairy") include_price_stats: Include min/max/avg prices (default: True)

query_spendingA

Query total spending with optional filters.

Use this tool to analyze spending patterns. Supports filtering by:

  • vendor: Store name (e.g., "Trader Joes", "Costco")

  • category: Category name (e.g., "produce", "dairy")

  • start_date: Start of date range (ISO format, e.g., "2025-01-01")

  • end_date: End of date range (ISO format, e.g., "2025-01-31")

Returns total spending, item count, and breakdown by category or vendor.

list_categoriesA

List all valid grocery categories.

Returns the fixed set of valid categories and shows which ones have items logged. Use these exact category names when adding items.

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

A3.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct action+resource: single-item price lookup, category listing, aggregate spending analysis, bulk insertion, and category enumeration. The two read tools that surface prices (query_item_price vs list_items_by_category) differ clearly in scope (one item's history vs all items in a category).

Naming Consistency5/5

All names follow a consistent snake_case verb_noun pattern (query_item_price, list_items_by_category, query_spending, add_grocery_items, list_categories). The query_/list_/add_ verb prefixes are used predictably.

Tool Count5/5

Five tools is well-scoped for a focused grocery logging server; each tool covers a distinct, non-redundant operation. No bloat or trivial padding.

Completeness3/5

The surface covers create and several read operations but lacks any update or delete tool, so agents cannot correct or remove mislogged purchases. Core workflows (log + query price/spending) are supported, but the lifecycle is incomplete.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources