Skip to main content
Glama
Sign In

Supplementenscanner

by nl.supplementenscanner
OverviewDiscussionsAdmin

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.

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. 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. 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"
+}
  2. 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."
  3. 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."
  4. 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."
  5. Changed1 schema field changed
    • changedInput schema / properties / market / description
      Previous value: -"Optional country market to query: nl, be. Defaults to the market of the requested domain. Any other value is rejected."New value: +"Optional country market to query: nl, be. Defaults to nl, the market this endpoint answers for. Any other value is rejected."
  6. Changed1 schema field changed
    • changedInput schema / properties / market / description
      Previous value: -"Optional country market to query: nl. Defaults to the market of the requested domain. Any other value is rejected."New value: +"Optional country market to query: nl, be. Defaults to the market of the requested domain. Any other value is rejected."
  7. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds real value by disclosing that subcategories are included and that responses list available_filters with invalid ids rejected, but says nothing about result ordering ties or pagination behavior.

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, front-loaded with the core purpose, then prerequisites and narrowing options. No filler.

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?

For a filtered list tool with full schema coverage and annotations carrying safety, the description covers prerequisite workflow, filtering contract, and response affordance (available_filters) without needing an output schema.

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 coverage is 100%, so all six parameters are already documented in the schema, and much of the description's filter guidance (available_filters, rejected ids) merely restates it. The description adds only modest context, so baseline 3 applies.

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 — finding cheapest supplements ranked by normalized price-per-unit within a category and its subcategories. The 'price-per-unit' normalization detail makes the ranking criterion unambiguous and separates it from get_product/search_products.

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

Usage Guidelines5/5

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

Explicitly frames itself as the primary tool for 'what is the cheapest X?' questions and tells the agent to call list_categories first for a valid slug. It also explains how to narrow results with filters and brand, leaving little inference.

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

All Supplementenscanner toolsInspect
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources