Skip to main content
Glama
sepehr071

technolife-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Deals

tl_deals
Read-onlyIdempotent

Fetch current in-stock discounts and timed home-page deals from Technolife. Filter by minimum percent off, sort by savings, and page through results.

Instructions

List current in-stock discounts (Technolife's main deal list, تکنوآف) and, on page 0, the timed home-page deals (تکنو تایم).

Use for "best deals right now". deal_ends is UTC. total is the whole deal list, before min_discount_pct. With biggest_percent or min_discount_pct each page scans the next 100 deals and returns the best limit; more_on_page counts matches cut off (raise limit). For one category use tl_category_products with sort=biggest_discount_toman.

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page.
sortNoOrder; biggest_percent re-sorts a page of the largest Toman discounts by percent.biggest_percent
limitNoMax deals to return (and max timed deals).
min_discount_pctNoOnly deals with at least this percent off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.3.0
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / min_discount_pct / title
      Removed value: -"Min Discount Pct"
    • changedInput schema / properties / page / description
      Previous value: -"Zero-based page number."New value: +"Zero-based page."
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"tl_dealsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "tl_dealsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description goes well past that: it discloses that deal_ends is UTC, that total counts the whole list before min_discount_pct is applied, that biggest_percent/min_discount_pct cause each page to scan the next 100 deals and return only the best `limit`, and that more_on_page signals matches cut off by the limit. These are non-obvious call/filter semantics that cannot be derived from the annotations or schema.

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?

Front-loaded with the core purpose and scope, then paging/filter caveats, then sibling routing — a sensible order with little filler. The dense compressed phrasing ('total is the whole deal list, before min_discount_pct') and the newline-broken layout cost it a point but nothing is truly wasted.

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 four optional params, no output schema, and no nested objects, the description covers the important gaps: what total and more_on_page mean, the timezone of deal_ends, and how paging interacts with sort/filter. It stops short of naming the actual fields of a returned deal record, but for a read-only list endpoint that is a minor omission.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains that biggest_percent re-sorts a page of the largest Toman discounts by percent (a subtle interaction with the default sort), that min_discount_pct filters against the untruncated `total`, and that page 0 additionally returns timed deals. That is genuine added semantics beyond the per-field schema text.

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+resource with scope: 'List current in-stock discounts' covering both the main deal list (تکنوآف) and the timed home-page deals (تکنو تایم) on page 0. It explicitly names the sibling to use for a narrower case (tl_category_products with sort=biggest_discount_toman), so an agent can separate this from the 18 other sibling tools without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ('Use for "best deals right now"') and an explicit routing rule away from this tool when the scope is a single category, naming the alternative tool and the exact sort value to pass. Both the when-to-use and the when-to-use-something-else conditions are stated rather than inferred.

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

Deploy Server

Other Tools