Skip to main content
Glama

LebTech - electronics prices in Lebanon

Price history

price_history
Read-only

How the lowest price of one product across its market's shops moved over the last ~90 days: current low, period low/high, the drop since tracking began, and weekly lows. 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": "price_history"
  }
}

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

A3.7/5.0
Behavior4/5

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

The annotations already establish read-only and non-open-world behavior, but the description adds meaningful scope: roughly 90 days of history, the lowest price across a market's shops, and the specific historical metrics returned. It does not cover edge cases such as untracked products or empty history, but for a simple read-only tool it adds solid behavioral context.

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 description is short, front-loads the historical price behavior, and then states accepted input forms. The second sentence slightly duplicates the product parameter schema, but it remains useful and does not bury the main point.

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 compensates by naming the historical values returned and the time window. Combined with the fully described two-parameter schema and read-only annotations, it is complete enough for correct invocation, though it omits behavior for missing or untracked products.

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%, so the product and market parameters are already fully documented. The description mainly repeats the accepted product identifier forms and leaves market semantics such as defaults and URL-driven inference to the schema, which is appropriate but not value-adding.

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 clearly states that this returns a product's lowest-price history across a market's shops over roughly 90 days, including current low, period low/high, drop, and weekly lows. It distinguishes itself from current-price siblings implicitly through the historical scope, but it never names an alternative explicitly.

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?

Historical use is strongly implied by 'moved over the last ~90 days' and the returned fields, so an agent can infer this is for trend/history rather than a current-price lookup. However, it gives no explicit when-to-use or when-not-to-use guidance versus `get_product_prices`, `cheapest_in_category`, or `search_products`.

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