Skip to main content
Glama
technolife-mcp

technolife-mcp

by sepehr071

Compare products

tl_compare
Read-onlyIdempotent

Compare 2–5 products side by side to check price, stock, rating, and full specs, helping you evaluate same-category electronics before choosing.

Instructions

Compare 2-5 products side by side: price, stock, rating and every spec.

specs is {section: {spec: values}}, one value per product in the order of products. Same-category products compare best. 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": {
      "product_codes": "<product_codes>"
    },
    "name": "tl_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_codesYes2 to 5 product codes, e.g. ['TLP-60492', 'TLP-133524'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • changedInput schema / properties / product_codes / items / 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_codes / title
      Removed value: -"Product Codes"
    • removedInput schema / title
      Removed value: -"tl_compareArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "tl_compareDictOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds the otherwise undocumented response shape 'specs is {section: {spec: values}}, one value per product in the order of products'. That ordering guarantee is genuinely useful behavioral context, though it says nothing about how mismatched categories or missing specs are represented.

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?

Three short sentences, front-loaded with what is compared, then the return shape, then routing. Nothing is padded, but the trailing 'For sellers use tl_product' is the weakest line and sits where a clearer exclusion rule would earn more value.

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 carries the burden of describing returns and does so with the section/spec/value structure and ordering. It remains slightly thin on degenerate cases (out-of-category products, unequal spec coverage) for a multi-product aggregation tool, so not fully complete.

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 a single required array parameter, so the schema already documents min/max items and the code pattern. The description contributes the alignment semantics (result values are ordered to match `products`), which is real added meaning, but it does not restate code format or array constraints — baseline 3 with a small lift.

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 ('Compare 2-5 products side by side') plus the exact comparison dimensions: price, stock, rating and every spec. The 2-5 cardinality bound is stated inline, and the sibling pointer to tl_product makes clear this is the multi-item counterpart to the single-product tool.

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?

'Same-category products compare best' is a real usage condition, and 'For sellers use tl_product' routes the agent to an alternative. However, the routing wording is slightly off given a dedicated tl_seller sibling exists, and no explicit when-not-to-use case or cross-category caveat beyond 'compare best' is given.

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