Skip to main content
Glama

Search Alphamega products

search_products
Read-only

Find products in the Alphamega catalogue by free-text query, brand, category, diet, price, promotion, or stock, and return compact records for price and availability checks.

Instructions

Search the Alphamega catalogue by free text and/or filters. Returns compact product records (id, title, brand, price, unit price, promotion, barcode, category, stock). Omit query to browse a category or list promotions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
dietNoDietary labels the product must carry (all of them).
sortNoResult order; defaults to relevance. Price sorting uses pack price, not unit price.
limitNoProducts to return (default 10).
queryNoFree-text query in English or Greek, e.g. "halloumi" or "γάλα". Omit to match everything.
brandsNoExact brand names (case-sensitive, as returned in `brand` or the brands facet), e.g. ["Charalambides Christis"]. Several brands are OR-ed.
offsetNoNumber of results to skip, for paging.
categoryNoCategory path from `list_categories`, e.g. "chilled > fresh milk, cooking cream & eggs". Matches the category and everything below it; case-insensitive.
price_maxNoMaximum pack price in EUR.
price_minNoMinimum pack price in EUR.
promotionNoOnly products in this promotion; "any" means any current promotion.
in_stock_atNoOnly products in stock at this store (or at any store). Omit to include out-of-stock products; each product reports `in_stock` either way.
include_facetsNoAlso return counts of brands, subcategories, dietary labels and promotions among the matches — useful to discover exact brand names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real context beyond that by enumerating the returned fields and clarifying that omitting `in_stock_at` includes out-of-stock products while each record still reports `in_stock`. It does not discuss rate limits or result-set size beyond the limit parameter, but what it adds is substantive.

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?

Three tight sentences: purpose, return shape, and the key usage trick. The most decision-relevant information is front-loaded and there is no filler.

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

Completeness4/5

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

For a 12-parameter, output-schemaless search tool this covers purpose, return fields, and the omit-query mode well enough to call it correctly. A brief note on how offset/limit interact with the 900-result-offset cap, or on facet discovery via `include_facets`, would close the remaining gap.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented with examples and defaults; the baseline of 3 applies. The description only reinforces the omit-`query` browsing mode, adding little semantic detail the schema does not already carry.

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

Purpose4/5

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

States a specific verb and resource ('Search the Alphamega catalogue by free text and/or filters') and immediately characterizes the result as compact product records. It never names the closer sibling get_products, so the agent must infer that differentiated behavior from that tool's own definition rather than from this one.

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

Usage Guidelines3/5

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

Gives one concrete usage pattern — omit `query` to browse a category or list promotions — which is genuinely actionable. It offers no exclusions or routing advice relative to get_products, suggest, or match_shopping_list, so guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.