Skip to main content
Glama
sepehr071

technolife-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Product details

tl_product
Read-onlyIdempotent

Get one product's offers by code: price per color, seller, warranty, stock, delivery, insurance, installment and BNPL pricing; use the seller item ID to compute a basket total.

Instructions

Get one product's offers: price per color, seller and warranty, stock, delivery time, insurance and installment prices.

Use after tl_search / tl_suggest. offers are cheapest cash price first; installment_price and bnpl_price are the same seller item in the installment (LOAN) and buy now pay later (BNPL) price lists, null if not offered. Pass seller_item_id to tl_price_basket for a final total.

Input Schema

NameRequiredDescriptionDefault
product_codeYesProduct code, e.g. 'TLP-60492' (bare number works).
include_specsNoInclude the spec table (a few KB).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.0
    • changedInput schema / properties / include_specs / description
      Previous value: -"Include the full spec table (adds a few KB)."New value: +"Include the spec table (a few KB)."
    • removedInput schema / properties / include_specs / title
      Removed value: -"Include Specs"
    • changedInput schema / properties / product_code / description
      Previous value: -"Product code from a search or list, e.g. 'TLP-60492' (the bare number works too)."New value: +"Product code, e.g. 'TLP-60492' (bare number works)."
    • removedInput schema / properties / product_code / title
      Removed value: -"Product Code"
    • removedInput schema / title
      Removed value: -"tl_productArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "tl_productDictOutput",
-  "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, openWorld), so the bar is lower. The description still adds real behavioral context beyond them: offers are sorted cheapest cash price first, and installment_price/bnpl_price are the same seller item in different price lists, null when not offered. Missing only peripheral details like pagination or result caps.

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 action, then two short paragraphs covering result semantics and workflow chaining. Every sentence carries information, though the dense second paragraph packs several field-level definitions into one breath.

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?

There is no output schema, so the description must convey the return shape — and it does, listing the price/seller/warranty/stock/delivery/insurance facets and the sort order. An agent has enough to call it and interpret the response, with only minor gaps around error cases or empty results.

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% and both parameters (product_code with its TLP- pattern, include_specs with default) are already documented there. The description adds no syntax or format guidance for the inputs; seller_item_id it mentions is an output field, not an input parameter. Baseline 3 applies.

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 and resource (get one product's offers) and enumerates the returned facets: price per color, seller, warranty, stock, delivery time, insurance and installment prices. This distinguishes it from sibling listing/search tools like tl_search and tl_compare, which the agent can rule out without opening schemas.

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?

Explicitly positions the tool in a workflow: 'Use after tl_search / tl_suggest' and 'Pass seller_item_id to tl_price_basket for a final total.' This names both the upstream alternatives that lead here and the downstream tool to call next, leaving nothing to inference.

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