Skip to main content
Glama

LebTech - electronics prices in Lebanon

Search LebTech / PriceTeq

search_products
Read-only

Find electronics and their live prices across a market's shops (Lebanon by default in USD; the Gulf, Iraq, Jordan and Egypt via market, in local currency; re-checked nightly). Returns up to 10 products, most widely sold first, each with its lowest price, how many shops sell it, and its page. Laptops also carry model_page: every CPU/GPU variant of that model with the same RAM/storage, which can start lower.

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWhat to look for, e.g. 'macbook air m4', 'rtx 5070 laptop', 'iphone 17 256gb'.
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.
categoryNoOptional: limit to one category.
max_priceNoOptional upper price limit, in the market's currency.
max_price_usdNoOptional upper 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": "Optional upper price limit, in the market's currency.",
      +  "type": "number"
      +}
    • changedInput schema / properties / max_price_usd / description
      Previous value: -"Optional upper price limit in USD."New value: +"Optional 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

A4.3/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, so safety is covered. The description still adds real behavioral value beyond them: data freshness (nightly re-check), result cap and ordering (up to 10, most widely sold first), per-item payload (lowest price, shop count, page), and the laptop-only model_page field with the caveat that variants "can start lower."

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?

Two sentences, front-loaded with purpose and scope before return details; every clause (default market, currency, refresh cadence, ordering, model_page) carries information an agent would otherwise have to guess. The parenthetical market list is slightly dense but not wasteful.

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?

With no output schema, the description responsibly explains the return shape, and it covers defaults and currency handling for a 6-parameter tool with 83% schema coverage. Minor gaps remain: nothing about zero-result behavior or how loose the query matching is (model vs. free-text).

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?

Schema coverage is 83%, so the baseline is 3; the description goes further by tying the 10-result cap to the `limit` bound, restating the default market and per-market currency behavior, and surfacing the model_page return field that has no input parameter of its own. The two currency filters (max_price vs max_price_usd) are left to the schema, so it is not a full 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?

"Find electronics and their live prices across a market's shops" states a specific verb (find) and resource (products with live prices), then scopes it geographically and by currency. An agent can distinguish this from price_history (time series), cheapest_in_category (category ranking), and get_product_prices (per-product) without opening any schema.

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?

It gives clear operating context: search by free-text query, Lebanon/USD by default, other markets via `market`, results re-checked nightly. It never explicitly excludes a sibling or says when to prefer price_history or cheapest_in_category, so it falls short of a 5.

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