Skip to main content
Glama

LebTech - electronics prices in Lebanon

Cheapest in a category

cheapest_in_category
Read-only

The cheapest products currently in stock in a category in one market (Lebanon by default; laptops: cheapest among sensible, new machines first). Optional budget and brand. Up to 10 results.

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": "<category>"
    },
    "name": "cheapest_in_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoExact brand, e.g. 'Lenovo', 'Apple', 'Samsung'.
limitNo
marketNoOptional market: LB (Lebanon, default), AE (UAE), SA (Saudi Arabia), QA (Qatar), JO (Jordan), OM (Oman), EG (Egypt), KW (Kuwait), BH (Bahrain) or IQ (Iraq). Prices come back in that market's currency.
categoryYes
max_priceNoUpper price limit, in the market's currency.
max_price_usdNoUpper price limit in USD (converted for non-USD markets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / market / description
      Previous value: -"Optional market: LB (Lebanon, default), AE (UAE), SA (Saudi Arabia), QA (Qatar), JO (Jordan), OM (Oman), EG (Egypt), KW (Kuwait) or BH (Bahrain). Prices come back in that market's currency."New value: +"Optional market: LB (Lebanon, default), AE (UAE), SA (Saudi Arabia), QA (Qatar), JO (Jordan), OM (Oman), EG (Egypt), KW (Kuwait), BH (Bahrain) or IQ (Iraq). Prices come back in that market's currency."
    • changedInput schema / properties / market / enum
      Previous value: -[
      -  "LB",
      -  "AE",
      -  "SA",
      -  "QA",
      -  "JO",
      -  "OM",
      -  "EG",
      -  "KW",
      -  "BH"
      -]New value: +[
      +  "LB",
      +  "AE",
      +  "SA",
      +  "QA",
      +  "JO",
      +  "OM",
      +  "EG",
      +  "KW",
      +  "BH",
      +  "IQ"
      +]
  2. Changed3 schema fields changed
    • addedInput schema / properties / market
      Added value: +{
      +  "description": "Optional market: LB (Lebanon, default), AE (UAE), SA (Saudi Arabia), QA (Qatar), JO (Jordan), OM (Oman), EG (Egypt), KW (Kuwait) or BH (Bahrain). Prices come back in that market's currency.",
      +  "enum": [
      +    "LB",
      +    "AE",
      +    "SA",
      +    "QA",
      +    "JO",
      +    "OM",
      +    "EG",
      +    "KW",
      +    "BH"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / max_price
      Added value: +{
      +  "description": "Upper price limit, in the market's currency.",
      +  "type": "number"
      +}
    • addedInput schema / properties / max_price_usd / description
      Added value: +"Upper price limit in USD (converted for non-USD markets)."
  3. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "laptop",
      -  "phone",
      -  "tablet",
      -  "monitor",
      -  "tv",
      -  "console",
      -  "audio",
      -  "component",
      -  "peripheral",
      -  "camera",
      -  "wearable",
      -  "appliance",
      -  "power",
      -  "networking",
      -  "printer",
      -  "storage",
      -  "game",
      -  "desktop",
      -  "smarthome",
      -  "creator"
      -]New value: +[
      +  "laptop",
      +  "phone",
      +  "tablet",
      +  "monitor",
      +  "tv",
      +  "console",
      +  "audio",
      +  "component",
      +  "peripheral",
      +  "camera",
      +  "wearable",
      +  "appliance",
      +  "power",
      +  "networking",
      +  "printer",
      +  "storage",
      +  "game",
      +  "desktop",
      +  "smarthome",
      +  "creator",
      +  "print3d"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "laptop",
      -  "phone",
      -  "tablet",
      -  "monitor",
      -  "tv",
      -  "console",
      -  "audio",
      -  "component",
      -  "peripheral",
      -  "camera",
      -  "wearable",
      -  "appliance",
      -  "power",
      -  "networking",
      -  "printer",
      -  "storage",
      -  "game",
      -  "desktop",
      -  "smarthome"
      -]New value: +[
      +  "laptop",
      +  "phone",
      +  "tablet",
      +  "monitor",
      +  "tv",
      +  "console",
      +  "audio",
      +  "component",
      +  "peripheral",
      +  "camera",
      +  "wearable",
      +  "appliance",
      +  "power",
      +  "networking",
      +  "printer",
      +  "storage",
      +  "game",
      +  "desktop",
      +  "smarthome",
      +  "creator"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "laptop",
      -  "phone",
      -  "tablet",
      -  "monitor",
      -  "tv",
      -  "console",
      -  "audio",
      -  "component",
      -  "peripheral",
      -  "camera",
      -  "wearable",
      -  "appliance",
      -  "power",
      -  "networking",
      -  "printer",
      -  "storage",
      -  "game",
      -  "desktop"
      -]New value: +[
      +  "laptop",
      +  "phone",
      +  "tablet",
      +  "monitor",
      +  "tv",
      +  "console",
      +  "audio",
      +  "component",
      +  "peripheral",
      +  "camera",
      +  "wearable",
      +  "appliance",
      +  "power",
      +  "networking",
      +  "printer",
      +  "storage",
      +  "game",
      +  "desktop",
      +  "smarthome"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "laptop",
      -  "phone",
      -  "tablet",
      -  "monitor",
      -  "tv",
      -  "console",
      -  "audio",
      -  "component",
      -  "peripheral",
      -  "camera",
      -  "wearable",
      -  "appliance",
      -  "power",
      -  "networking",
      -  "printer"
      -]New value: +[
      +  "laptop",
      +  "phone",
      +  "tablet",
      +  "monitor",
      +  "tv",
      +  "console",
      +  "audio",
      +  "component",
      +  "peripheral",
      +  "camera",
      +  "wearable",
      +  "appliance",
      +  "power",
      +  "networking",
      +  "printer",
      +  "storage",
      +  "game",
      +  "desktop"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "laptop",
      -  "phone",
      -  "tablet",
      -  "monitor",
      -  "tv",
      -  "console",
      -  "audio",
      -  "component",
      -  "peripheral",
      -  "camera",
      -  "wearable",
      -  "appliance"
      -]New value: +[
      +  "laptop",
      +  "phone",
      +  "tablet",
      +  "monitor",
      +  "tv",
      +  "console",
      +  "audio",
      +  "component",
      +  "peripheral",
      +  "camera",
      +  "wearable",
      +  "appliance",
      +  "power",
      +  "networking",
      +  "printer"
      +]
  8. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "laptop",
      -  "phone",
      -  "tablet",
      -  "monitor",
      -  "tv",
      -  "console",
      -  "audio",
      -  "component",
      -  "peripheral",
      -  "camera",
      -  "wearable"
      -]New value: +[
      +  "laptop",
      +  "phone",
      +  "tablet",
      +  "monitor",
      +  "tv",
      +  "console",
      +  "audio",
      +  "component",
      +  "peripheral",
      +  "camera",
      +  "wearable",
      +  "appliance"
      +]
  9. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds genuinely new behavioral context: results are restricted to currently in-stock items, limited to a single market, capped at 10 results, and for laptops ranked 'among sensible, new machines first' — a curation heuristic found nowhere in the structured fields. It still omits how ties are broken, currency conversion behavior for price comparisons, and what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core scope — cheapest, in-stock, one category, one market — is front-loaded in the first clause, and the two follow-up sentences are short and purposeful. The nested parenthetical is dense but carries real information rather than filler.

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

Completeness3/5

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

For a six-parameter tool with no output schema, the description says nothing about the shape of the returned results — whether each item includes price, currency, availability, or a link. It also leaves the default for limit and the interaction of the two price caps unexplained, which matters for a tool whose whole point is a ranked short list.

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 67%, so most parameters are already documented, and the description only restates the budget and brand filters plus the Lebanon default. It does not clarify the relationship between max_price (market currency) and max_price_usd, nor the limit default, which are the two spots where the schema is thinnest.

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?

The description states a specific verb and resource: the cheapest in-stock products within one category and one market. The parenthetical default (Lebanon) and the laptop-specific curation note sharpen the scope. It does not explicitly name how it differs from siblings like get_product_prices or search_products, so it stops short of 5.

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?

Usage is implied rather than stated: an agent can infer this is the tool for budget-first, single-category lookups with optional brand/price filters. There is no explicit when-not guidance and no reference to the sibling tools (price_history, search_products, get_product_prices), leaving the agent to guess which one to pick for a broad search versus a price lookup.

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.

Resources