Skip to main content
Glama
technolife-mcp

technolife-mcp

by sepehr071

Find cheapest products

tl_find_cheapest
Read-onlyIdempotent

Find in-stock products matching a query and return one flat list sorted by discounted price. Narrow results by category, brand, and price range.

Instructions

Find the cheapest in-stock products for a search, one flat list sorted by the price after discount.

Accessories often match a model name: check categories and brands, then call again with category_code and brand_codes. Prices are the featured offer: confirm with tl_product.

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": "tl_find_cheapest"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax products to return.
pagesNoPages of 100 results to scan.
queryYesProduct name, Persian or English, e.g. 'آیفون 16'.
max_priceNoHighest price in Toman, e.g. 150000000.
min_priceNoLowest price in Toman, e.g. 50000000.
brand_codesNoCodes from `brands` of a result or tl_find_brand, e.g. [16, 19].
category_codeNoCode from `categories` of a result, e.g. 1 (phones), to skip accessories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv0.5.0
    • removedInput schema / properties / brand_codes / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "minimum": 1,
      -      "type": "integer"
      -    },
      -    "maxItems": 10,
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / brand_codes / description
      Previous value: -"Brand codes from `brands` of a result or tl_find_brand, e.g. [16, 19]."New value: +"Codes from `brands` of a result or tl_find_brand, e.g. [16, 19]."
    • addedInput schema / properties / brand_codes / items
      Added value: +{
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / brand_codes / maxItems
      Added value: +10
    • addedInput schema / properties / brand_codes / type
      Added value: +[
      +  "array",
      +  "null"
      +]
    • removedInput schema / properties / category_code / anyOf
      Removed value: -[
      -  {
      -    "minimum": 1,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / category_code / description
      Previous value: -"Category code from `categories` of tl_search / tl_find_cheapest, e.g. 1 (phones), to skip accessories."New value: +"Code from `categories` of a result, e.g. 1 (phones), to skip accessories."
    • addedInput schema / properties / category_code / minimum
      Added value: +1
    • addedInput schema / properties / category_code / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedInput schema / properties / max_price / anyOf
      Removed value: -[
      -  {
      -    "minimum": 0,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / max_price / minimum
      Added value: +0
    • addedInput schema / properties / max_price / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedInput schema / properties / min_price / anyOf
      Removed value: -[
      -  {
      -    "minimum": 0,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / min_price / minimum
      Added value: +0
    • addedInput schema / properties / min_price / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
  2. Changed13 schema fields changedv0.3.0
    • changedInput schema / properties / brand_codes / description
      Previous value: -"Brand filter codes from the `brands` list of a result or tl_find_brand, e.g. [16] (Lenovo) or [16, 19] (Lenovo or ASUS)."New value: +"Brand codes from `brands` of a result or tl_find_brand, e.g. [16, 19]."
    • removedInput schema / properties / brand_codes / title
      Removed value: -"Brand Codes"
    • changedInput schema / properties / category_code / description
      Previous value: -"Category filter code from the `categories` list of a tl_search / tl_find_cheapest result, e.g. 1 (mobile phones), to skip accessories."New value: +"Category code from `categories` of tl_search / tl_find_cheapest, e.g. 1 (phones), to skip accessories."
    • removedInput schema / properties / category_code / title
      Removed value: -"Category Code"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / max_price / title
      Removed value: -"Max Price"
    • removedInput schema / properties / min_price / title
      Removed value: -"Min Price"
    • changedInput schema / properties / pages / description
      Previous value: -"Pages of 100 cheapest-indexed results to scan."New value: +"Pages of 100 results to scan."
    • removedInput schema / properties / pages / title
      Removed value: -"Pages"
    • changedInput schema / properties / query / description
      Previous value: -"Product name or words, Persian or English, e.g. 'آیفون 16' or 'لپ تاپ لنوو'."New value: +"Product name, Persian or English, e.g. 'آیفون 16'."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"tl_find_cheapestArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "tl_find_cheapestDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), so the bar is lower. The description still adds two useful behavioral facts not in annotations: results are restricted to in-stock items and prices reflect the 'featured offer' rather than a guaranteed checkout price. It says nothing about pagination/scan behavior or response fields, leaving meaningful gaps for a 7-parameter tool.

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?

Four short sentences, front-loaded with the core purpose, then the refinement workflow, then the price caveat. No filler, though the opening line reads slightly awkwardly and the workflow paragraph could be tightened into one clause.

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?

With no output schema, the description carries the burden of describing return values, and it only says 'one flat list sorted by the price after discount' without naming fields or what a single entry contains. It covers the important workflow and price caveat but leaves the agent guessing about result structure and how `pages` affects coverage.

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 baseline is 3. The description does add genuine meaning beyond the schema by explaining the purpose of the category_code/brand_codes pairing (filtering out accessories that match a model name), but it says nothing about `limit`, `pages`, or the price-range parameters that the schema already covers.

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 gives a specific verb and resource ('find the cheapest in-stock products') plus the result shape and ordering rule ('one flat list sorted by the price after discount'), which is far more than a restatement of the name. It does not explicitly differentiate itself from siblings like tl_search, tl_deals, or tl_compare, so an agent must infer that this one is the price-minimizing variant.

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 supplies a concrete usage loop: when accessories pollute results, inspect `categories`/`brands` and re-call with category_code and brand_codes. It also names a verification step ('confirm with tl_product'), which implies this tool's prices are indicative rather than authoritative. It stops short of stating when to prefer this over tl_search or tl_deals, so it is clear context without full alternative routing.

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