Skip to main content
Glama

LebTech - electronics prices in Lebanon

Prices for one product

get_product_prices
Read-only

Live per-shop prices for ONE product: every shop in its market that has the identical configuration in stock, cheapest first, with links to the shop's own product page. Takes a product id or a lebtechlb.com / priceteq.com product or laptop URL.

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": {
      "product": "<product>"
    },
    "name": "get_product_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. A priceteq.com URL sets it by itself.
productYesA product id, or a lebtechlb.com /product/ or /laptop/ URL, or a priceteq.com /<market>/product/ URL.

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. A priceteq.com URL sets it by itself."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. A priceteq.com URL sets it by itself."
    • 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. Changed2 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. A priceteq.com URL sets it by itself.",
      +  "enum": [
      +    "LB",
      +    "AE",
      +    "SA",
      +    "QA",
      +    "JO",
      +    "OM",
      +    "EG",
      +    "KW",
      +    "BH"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / product / description
      Previous value: -"A product id or a lebtechlb.com /product/ or /laptop/ URL."New value: +"A product id, or a lebtechlb.com /product/ or /laptop/ URL, or a priceteq.com /<market>/product/ URL."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's job is to add behavior, and it does: results are restricted to shops with the identical configuration in stock, sorted cheapest first, and include outbound links to the shop's own page. It stays consistent with openWorldHint=false by describing a bounded, market-local result set. It does not mention how empty or out-of-stock markets are reported, which keeps it short of a 5.

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?

Two sentences, no filler, and the scoping constraint and result shape are front-loaded before the input forms. Every clause carries information an agent would otherwise have to guess.

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 must carry the return shape and does: per-shop prices, ordering, stock/configuration constraint, and link inclusion. For a 2-parameter read tool this is close to complete; only edge-case behavior (no shops carrying the configuration) is unaddressed.

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%, and both the accepted id/URL forms and the fact that a priceteq.com URL sets the market implicitly are already documented in the schema. The description restates those accepted inputs without adding syntax, validation, or fallback rules, 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 (live per-shop prices) and scopes it hard with "ONE product", which separates it from the category-level siblings like cheapest_in_category and search_products. It also names what comes back: every in-stock shop with the identical configuration, cheapest first, with links.

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?

The capitalized "ONE product" implies this is the single-product lookup versus the category/browse siblings, but no alternative is named and there is no explicit when-not guidance. Usage is inferable rather than stated, which is the definition of minimum-viable here.

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