MealCP MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsA | Search the grocery product catalog by keyword with faceted filtering. Returns matching products with name, brand, price, unit price, retailer and a URL, plus facet counts for retailers, brands and countries. Args:
q: Free-text query (e.g. "potatoes", "krumpli"). Empty returns all,
sorted by Returns: A structured search response. Raises: mcp.server.mcpserver.exceptions.ToolError: If the search API is unavailable; the message starts with the API's stable error token. |
| get_price_historyA | Get aggregated price-history stats for one product over a date range. Returns min/max/avg/first/last price plus the net change over the window,
pooled across every store carrying the product. Pair with Args:
product_id: Opaque product id from a search hit (e.g.
Returns: Aggregated price-history stats. Raises: mcp.server.mcpserver.exceptions.ToolError: If the API is unavailable or the product is not found; the message starts with the API's stable error token. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: catalog search versus price-history retrieval for a specific product. There is no overlap in function or ambiguity about when to use each.
Both tool names follow a consistent snake_case verb_noun pattern: search_products and get_price_history. The convention is predictable and readable.
Only two tools exist for a grocery catalog and price-history server. While they are focused, the surface feels thin for the apparent domain, which likely needs more lookup or discovery operations.
Search is broad and returns useful facets, and price history works when paired with search. However, notable gaps remain: no direct product-detail lookup, no category/retailer/brand listing endpoints, and no multi-product comparison tools.