Skip to main content
Glama
sepehr071

technolife-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Categories

tl_categories
Read-onlyIdempotent

Find Technolife category pages and URLs: search menu categories by name, list a category's brand and series sub-pages, or browse top-level categories and child titles.

Instructions

Find category pages and their urls for tl_category_products.

  • With query: categories anywhere in the menu whose name matches (best way to get a url).

  • With url: that category's sub-pages (brand and series pages).

  • With neither: the top-level categories and the titles of their children (get a child's url with query).

Input Schema

NameRequiredDescriptionDefault
urlNoList this category's sub-pages (brands, series), e.g. 'category/mobile/mobile-phone'.
queryNoCategory name part, e.g. 'لپ تاپ گیمینگ'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.0
    • changedInput schema / properties / query / description
      Previous value: -"Find categories whose name contains this, e.g. 'لپ تاپ گیمینگ' or 'هدفون'."New value: +"Category name part, e.g. 'لپ تاپ گیمینگ'."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • changedInput schema / properties / url / description
      Previous value: -"List the sub-pages (brands, series) of this category, e.g. 'category/mobile/mobile-phone'."New value: +"List this category's sub-pages (brands, series), e.g. 'category/mobile/mobile-phone'."
    • removedInput schema / properties / url / title
      Removed value: -"Url"
    • removedInput schema / title
      Removed value: -"tl_categoriesArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "tl_categoriesDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.6/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, and the description adds genuinely new behavior: the return shape changes with the mode (matching categories, sub-pages, or top-level categories plus child titles). It stops short of noting pagination, result limits, or whether empty results occur.

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?

A single purpose sentence followed by three one-line mode bullets, front-loaded and waste-free. The formatting maps directly onto the parameter combinations an agent must choose between.

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 return-value burden and does explain what each mode yields. It leaves unspecified whether the returned urls are relative or absolute strings and how results are bounded, which an agent would want before chaining into tl_category_products.

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 a 3 would be the baseline, but the description goes beyond the schema descriptions by explaining what happens when each parameter is supplied versus omitted, and how the two parameters interact (query for the menu-wide search, url for drilling into sub-pages).

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 ("Find category pages and their urls") and ties itself explicitly to the sibling tool it feeds, tl_category_products. An agent can distinguish it from tl_search or tl_product without opening any 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?

Enumerates all three invocation modes (query, url, neither) with the outcome of each, and even ranks one mode as "best way to get a url." This is explicit when-to-use guidance rather than implied context.

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