Skip to main content
Glama
technolife-mcp

technolife-mcp

by sepehr071

Categories

tl_categories
Read-onlyIdempotent

Find category page URLs and menu matches for Technolife products, or list top-level categories and sub-pages like brands and series using a query or category URL.

Instructions

Find category pages and their urls for tl_category_products.

With query: matching categories anywhere in the menu (best way to get a url). With url: that category's sub-pages (brands, series). With neither: top-level categories and child titles.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tl_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoCategory whose sub-pages to list, e.g. 'category/mobile/mobile-phone'.
queryNoCategory name part, e.g. 'لپ تاپ گیمینگ'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.5.0
    • removedInput schema / properties / query / anyOf
      Removed value: -[
      -  {
      -    "minLength": 2,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / query / minLength
      Added value: +2
    • addedInput schema / properties / query / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / url / anyOf
      Removed value: -[
      -  {
      -    "pattern": "^/?category/\\S+$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / url / description
      Previous value: -"List this category's sub-pages (brands, series), e.g. 'category/mobile/mobile-phone'."New value: +"Category whose sub-pages to list, e.g. 'category/mobile/mobile-phone'."
    • addedInput schema / properties / url / pattern
      Added value: +"^/?category/\\S+$"
    • addedInput schema / properties / url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. 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
  3. 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, open-world, so safety needs no restating. The description adds real behavioral content beyond them: with no arguments it returns top-level categories plus child titles, with url it returns sub-pages such as brands and series, with query it searches the whole menu. Missing only things like result size or pagination, which matters less for a browsing call.

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?

Three short mode clauses, front-loaded with the purpose sentence and each parameter mode given one compact line. No filler, no repetition of schema or annotation content.

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 results, and it does so for each of the three call modes. What remains unstated (result limits, ordering, error behavior for an unmatched url) is minor for a read-only discovery tool.

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 baseline is 3. Beyond the schema's 'Category whose sub-pages to list', the description clarifies that query matches anywhere in the menu (not just top level) and that url yields sub-pages like brands and series, which meaningfully frames what each parameter retrieves.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 names the downstream tool (tl_category_products) whose URLs it feeds, which distinguishes it from tl_category_filters and tl_category_products. It stops short of saying what makes it distinct from tl_find_brand for the brands case, so it is clear but not fully sibling-differentiated.

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?

Explicitly maps each parameter mode to a use case ('With query: matching categories anywhere in the menu (best way to get a url). With url: that category's sub-pages'), including a recommendation of which mode to prefer. It does not state when a different sibling tool would be a better choice, so no exclusions are given.

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