Skip to main content
Glama

Find cheapest products

find_cheapest
Read-onlyIdempotent

Find the cheapest supplements by normalized price-per-unit within a category (and all its subcategories). This is the primary tool for "what is the cheapest X?" questions. Use list_categories first to pick a valid category_slug. Narrow it with filters (the category page's attribute filters, such as vegan or a form) and brand; every response lists the filters the category offers in available_filters.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category_slug": "<category_slug>"
    },
    "name": "find_cheapest"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoOptional: only this brand, by name or slug as it appears in the results.
limitNoMaximum number of products to return (1-50).
marketNoOptional country market to query: nl, be, fr, gb, pl, es, dk, at, de, cz, pt, se, it, ch. Defaults to nl, the market this endpoint answers for. Any other value is rejected.
filtersNoOptional: only products carrying every one of these attributes, the filters of the category page, e.g. ["is_vegan", "is_lab_tested", "form:powder"]. A boolean attribute is its key; an option is "key:value", one value per key. Every response lists the ids this category offers in available_filters; an id it does not offer is rejected.
category_slugYesThe category to search within, e.g. "whey-protein" or "creatine". Products in every subcategory are included, so a parent slug like "protein-powder" works too. Get valid slugs from list_categories.
in_stock_onlyNoWhen true, only return products currently in stock.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / market / description
      Previous value: -"Optional country market to query: nl, be, fr, gb, pl, es, dk, at, de, cz, pt, se, it. Defaults to nl, the market this endpoint answers for. Any other value is rejected."New value: +"Optional country market to query: nl, be, fr, gb, pl, es, dk, at, de, cz, pt, se, it, ch. Defaults to nl, the market this endpoint answers for. Any other value is rejected."
  2. Changed1 schema field changed
    • changedInput schema / properties / market / description
      Previous value: -"Optional country market to query: nl, be, fr, gb, pl, es, dk, at, de, cz, pt, se. Defaults to nl, the market this endpoint answers for. Any other value is rejected."New value: +"Optional country market to query: nl, be, fr, gb, pl, es, dk, at, de, cz, pt, se, it. Defaults to nl, the market this endpoint answers for. Any other value is rejected."
  3. Changed1 schema field changed
    • changedInput schema / properties / market / description
      Previous value: -"Optional country market to query: nl, be, fr, gb, pl, es, dk, at, de, cz, pt. Defaults to nl, the market this endpoint answers for. Any other value is rejected."New value: +"Optional country market to query: nl, be, fr, gb, pl, es, dk, at, de, cz, pt, se. Defaults to nl, the market this endpoint answers for. Any other value is rejected."
  4. Changed1 schema field changed
    • changedInput schema / properties / market / description
      Previous value: -"Optional country market to query: nl, be, fr, gb, pl, es, dk, at, de, cz. Defaults to nl, the market this endpoint answers for. Any other value is rejected."New value: +"Optional country market to query: nl, be, fr, gb, pl, es, dk, at, de, cz, pt. Defaults to nl, the market this endpoint answers for. Any other value is rejected."
  5. Changed1 schema field changed
    • changedInput schema / properties / market / description
      Previous value: -"Optional country market to query: nl, be, fr, gb, pl, es, dk, at. Defaults to nl, the market this endpoint answers for. Any other value is rejected."New value: +"Optional country market to query: nl, be, fr, gb, pl, es, dk, at, de, cz. Defaults to nl, the market this endpoint answers for. Any other value is rejected."
  6. Changed2 schema fields changed
    • addedInput schema / properties / brand
      Added value: +{
      +  "description": "Optional: only this brand, by name or slug as it appears in the results.",
      +  "type": "string"
      +}
    • addedInput schema / properties / filters
      Added value: +{
      +  "description": "Optional: only products carrying every one of these attributes, the filters of the category page, e.g. [\"is_vegan\", \"is_lab_tested\", \"form:powder\"]. A boolean attribute is its key; an option is \"key:value\", one value per key. Every response lists the ids this category offers in available_filters; an id it does not offer is rejected.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  7. Changed1 schema field changed
    • changedInput schema / properties / market / description
      Previous value: -"Optional country market to query: nl, be, fr, gb, pl, es, dk. Defaults to nl, the market this endpoint answers for. Any other value is rejected."New value: +"Optional country market to query: nl, be, fr, gb, pl, es, dk, at. Defaults to nl, the market this endpoint answers for. Any other value is rejected."
  8. Changed1 schema field changed
    • changedInput schema / properties / market / description
      Previous value: -"Optional country market to query: nl, be, fr, gb, pl, es. Defaults to nl, the market this endpoint answers for. Any other value is rejected."New value: +"Optional country market to query: nl, be, fr, gb, pl, es, dk. Defaults to nl, the market this endpoint answers for. Any other value is rejected."
  9. Changed1 schema field changed
    • changedInput schema / properties / market / description
      Previous value: -"Optional country market to query: nl, be. Defaults to nl, the market this endpoint answers for. Any other value is rejected."New value: +"Optional country market to query: nl, be, fr, gb, pl, es. Defaults to nl, the market this endpoint answers for. Any other value is rejected."
  10. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the description's added context is genuine value: ranking is by normalized price-per-unit, subcategories are included, and invalid filter ids or markets are rejected. It still does not describe what a result entry contains (price, unit, stock) or how limit interacts with ranking.

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 sentences, front-loaded with the core purpose before the routing statement and the filter workflow. The parenthetical about subcategories is load-bearing rather than redundant, and nothing is padding.

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 six-parameter, read-only query tool with no output schema, it covers the prerequisite, filter discovery, and ranking basis. The main residual gap is that an agent is not told what a returned product record looks like beyond available_filters.

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

Parameters4/5

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

With 100% schema coverage the baseline is 3, and the description adds one thing the schema does not: every response enumerates the valid filter ids in available_filters, closing the discovery loop for the filters parameter. Otherwise it largely restates the schema's own filter/brand guidance, hence not a 5.

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?

States a specific verb and resource ('find the cheapest supplements by normalized price-per-unit within a category') plus scope ('and all its subcategories'), which immediately separates it from the generic search_products and get_product siblings. The line 'This is the primary tool for "what is the cheapest X?" questions' gives an agent a direct routing rule.

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?

Explicitly states the prerequisite workflow ('Use list_categories first to pick a valid category_slug') and how to narrow results via filters and brand. It does not state when NOT to use it (e.g., use search_products for keyword browsing), so it falls short of a full when/when-not/alternatives treatment.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.