Skip to main content
Glama
technolife-mcp

technolife-mcp

by sepehr071

Search products

tl_search
Read-onlyIdempotent

Search Technolife products by name, then filter by price, brand, category, stock, and sorting to compare prices, discounts, and ratings.

Instructions

Search Technolife products with prices, discount, stock and rating.

Also returns top categories and brands with codes: pass them back as category_code or brand_codes to narrow. For the lowest price use tl_find_cheapest; for sellers use 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_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page. Relevance pages can repeat items; page with another sort.
sortNoPrice and discount sorts are re-sorted on the price after discount.relevance
limitNoProducts per page.
queryYesProduct name, Persian or English, e.g. 'آیفون 16'.
in_stockNoOnly orderable products.
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. Changed17 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"
      +]
    • changedInput schema / properties / page / description
      Previous value: -"Zero-based page. Relevance pages can repeat items; page with a price, newest or best_selling sort."New value: +"Zero-based page. Relevance pages can repeat items; page with another sort."
    • changedInput schema / properties / sort / description
      Previous value: -"Order; price and discount sorts are re-sorted on the real price after discount."New value: +"Price and discount sorts are re-sorted on the price after discount."
  2. Changed17 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"
    • changedInput schema / properties / in_stock / description
      Previous value: -"Only products that can be ordered now."New value: +"Only orderable products."
    • removedInput schema / properties / in_stock / title
      Removed value: -"In Stock"
    • 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 / page / description
      Previous value: -"Zero-based page number. Relevance pages can repeat items; page with a price, newest or best_selling sort."New value: +"Zero-based page. Relevance pages can repeat items; page with a price, newest or best_selling sort."
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • 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"
    • changedInput schema / properties / sort / description
      Previous value: -"Order; cheapest, most_expensive and biggest_discount_toman are re-sorted on the real price after discount."New value: +"Order; price and discount sorts are re-sorted on the real price after discount."
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"tl_searchArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "tl_searchDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is fully covered without the description's help. The description adds useful behavior: the result set carries category and brand codes that are meant to be fed back as filters. It says nothing about result volume, pagination limits, or empty-result behavior, which would matter for a search tool with no output schema.

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 tight sentences: purpose and return payload first, then the refinement workflow and sibling alternatives. Nothing is redundant and the actionable routing information is not buried.

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 nine parameters and no output schema, the description does the necessary work of naming what comes back and how to chain the returned codes into a follow-up call. It is close to complete, though it omits any hint about result-set size or how deep paging behaves for a large catalog.

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 100% and the schema descriptions are already rich (page repetition under relevance, post-discount re-sorting, code provenance for brand_codes/category_code), so the baseline is 3. The description's contribution is mainly the round-trip framing of feeding returned codes back in, which the schema already hints at per-parameter, so it adds only modest meaning.

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 opens with a concrete verb and resource ('Search Technolife products') and immediately enumerates the returned facets (prices, discount, stock, rating), so the agent knows exactly what the call produces. It differentiates itself from tl_find_cheapest and tl_product by name, though it does not distinguish itself from catalog-browsing siblings such as tl_category_products or tl_suggest.

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 routes the agent explicitly for two cases ('For the lowest price use tl_find_cheapest; for sellers use tl_product') and describes an iterative narrowing workflow via category_code/brand_codes. It stops short of stating when NOT to use it, e.g. when the user only wants to browse a category without a query string.

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