Skip to main content
Glama
sepehr071

technolife-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Price a basket

tl_price_basket
Read-onlyIdempotent

Calculate the total cost for up to 20 seller items with discounts, insurance, quantity limits, and cash or installment pricing to compare order costs before purchase.

Instructions

Get the exact total for a set of seller items: discounts, insurance, quantity limits, cash vs installment price.

Priced as a guest; nothing is saved. max_count is the most units one order may contain; over_max_count means the site refuses that quantity. Each seller_item_id may appear once: compare cash and installment in separate calls.

Input Schema

NameRequiredDescriptionDefault
itemsYesSeller items to price, from tl_product offers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.3.0
    • removedInput schema / $defs / BasketItem / properties / count / title
      Removed value: -"Count"
    • removedInput schema / $defs / BasketItem / properties / insured_count / title
      Removed value: -"Insured Count"
    • removedInput schema / $defs / BasketItem / properties / payment / title
      Removed value: -"Payment"
    • removedInput schema / $defs / BasketItem / properties / seller_item_id / title
      Removed value: -"Seller Item Id"
    • removedInput schema / $defs / BasketItem / title
      Removed value: -"BasketItem"
    • removedInput schema / properties / items / title
      Removed value: -"Items"
    • removedInput schema / title
      Removed value: -"tl_price_basketArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "tl_price_basketDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds genuinely new behavioral context beyond them: pricing is done as a guest and nothing is persisted, plus it explains result semantics (max_count, over_max_count meaning the site refuses the quantity).

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-loads purpose in the first clause and stays compact. The trailing sentences about max_count/over_max_count are terse and arrive without framing them as response fields, which slightly hurts readability, but nothing is padded.

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 partially compensates by explaining max_count/over_max_count return semantics and the guest/no-save behavior. It is close to complete, though the return shape (totals, per-item breakdown) is still only partially described.

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 coverage is 100%, so the nested BasketItem fields are already documented. The description still adds a constraint absent from the schema — that each seller_item_id may appear only once and comparisons must be separate calls — which is real value beyond the structured fields.

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 ('Get the exact total for a set of seller items') and enumerates what the pricing covers: discounts, insurance, quantity limits, cash vs installment. This clearly distinguishes it from browsing siblings like tl_product and tl_compare.

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?

Gives concrete usage constraints: guest pricing, nothing saved, each seller_item_id may appear once, and compare cash vs installment in separate calls. It does not explicitly name sibling alternatives (e.g. tl_product for offer lookup), so routing guidance is implicit rather than explicit.

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