Skip to main content
Glama
sepehr071

technolife-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Seller

tl_seller
Read-onlyIdempotent

Retrieve a Technolife marketplace seller's rating, on-time and fault-free percentages, tenure, and products to judge offers before recommending them.

Instructions

Get a marketplace seller's reputation (rating 0-5, on-time %, fault-free %, time on Technolife) and its products.

Use to judge a seller found in tl_product offers before recommending its offer.

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page.
sortNoOrder of the seller's products.best_selling
limitNoProducts per page.
in_stockNoOnly orderable products.
seller_codeYesSeller code from tl_product offers, e.g. 'TLS-15172' (bare number works).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.3.0
    • 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"
    • changedInput schema / properties / page / description
      Previous value: -"Zero-based page number."New value: +"Zero-based page."
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • changedInput schema / properties / seller_code / description
      Previous value: -"Seller code from tl_product offers, e.g. 'TLS-15172' (the bare number works too)."New value: +"Seller code from tl_product offers, e.g. 'TLS-15172' (bare number works)."
    • removedInput schema / properties / seller_code / title
      Removed value: -"Seller Code"
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"tl_sellerArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "tl_sellerDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value beyond that by disclosing the return payload — reputation metrics plus the seller's product list — which matters since no output schema exists. It does not mention pagination behavior of the embedded product list.

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: the first defines the payload, the second gives the usage rule. Front-loaded and free of filler, with every clause earning its place.

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 does the necessary work of naming the returned reputation metrics and noting the seller's products are included. The only gap is that it doesn't signal the product list is paged (default 20, max 50), which the agent must infer from the schema.

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%, with every parameter documented including the seller_code pattern and the sort enum, so the schema carries the burden. The description adds no additional parameter meaning (no note on paging through a large catalog or how in_stock/sort interact with the reputation result), so the 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 a marketplace seller's reputation ... and its products') and enumerates the exact fields returned (rating 0-5, on-time %, fault-free %, time on Technolife). It also positions itself in the workflow relative to the tl_product sibling, so an agent can tell what this tool is for without opening the schema.

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 a clear when-to-use rule: judge a seller surfaced in tl_product offers before recommending that offer. It establishes the discovery-to-evaluation flow but names no exclusions or explicit alternative (e.g., how it differs from tl_store_info or tl_shop_reviews if those overlap).

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