Skip to main content
Glama
MealCP

MealCP MCP

Official
by MealCP

search_products

Search grocery product catalogs by keyword with filters for country, retailer, brand, category, and price to find matching products with pricing and retailer info.

Instructions

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 sort or recency. country: ISO 3166-1 alpha-2 country code (e.g. HU, FR). retailer: Retailer slug (e.g. tesco-hu, auchan-fr). chain: Chain slug (e.g. tesco, auchan). brand: Brand free-text token. tag: Tag slug (e.g. vegan). category: Category slug at any level (L1/L2/L3, e.g. fresh-produce, dairy-eggs, vegetables/potatoes); matches the whole subtree. city: City free-text token filtering stores carrying the product. currency: ISO 4217 currency code (e.g. HUF, EUR). min_price: Minimum latest price (inclusive). max_price: Maximum latest price (inclusive). sort: Stable sort token: relevance, newest, oldest, price_asc, price_desc, unit_price_asc, unit_price_desc. page: 1-indexed result page. page_size: Hits per page (1-100).

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNo
tagNo
cityNo
pageNo
sortNo
brandNo
chainNo
countryNo
categoryNo
currencyNo
retailerNo
max_priceNo
min_priceNo
page_sizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsYes
pageYes
foundYes
queryYes
facetsYes
page_sizeYes
Behavior4/5

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

No annotations are provided, so the description carries full responsibility. It discloses return format, error behavior (ToolError with stable token), and sorting semantics. It does not mention rate limits or authentication, but for a read-only search tool this is a minor gap. The description adds meaningful context beyond the minimal schema.

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 well-structured: a one-sentence summary front-loads the purpose, followed by a return summary, then a systematic Args list, and finally error/raises info. Every sentence earns its place; the long Args list is necessary for 14 parameters and is presented compactly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (14 params, no annotations, output schema exists but not shown), the description covers all essential aspects: what it returns, how to use each parameter, sorting, pagination, and error behavior. It even provides examples. Nothing critical for correct invocation is missing.

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

Parameters5/5

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

Schema description coverage is 0%, and the description compensates fully with a detailed Args list. Each parameter is explained with formats, examples, constraints (ISO codes, slugs, inclusive bounds, page_size limits), and semantic nuances. This is a model of parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Search the grocery product catalog by keyword with faceted filtering.' This is a specific verb+resource combination that immediately distinguishes it from its sibling (get_price_history), which focuses on historical data. The summary line also lists return fields, reinforcing the tool's scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context on how to use the tool (e.g., empty q returns all, sort options, category subtree matching), and its purpose is so distinct from the sibling that an agent can infer usage. However, it does not explicitly mention alternatives or state when not to use it, so it misses the 'explicit when/when-not' criterion for a 5.

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/MealCP/mealcp-mcp-python'

If you have feedback or need assistance with the MCP directory API, please join our Discord server