Skip to main content
Glama
sepehr071

technolife-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Find brand

tl_find_brand
Read-onlyIdempotent

Look up a Persian brand name to retrieve its filter code and brand page for Technolife catalog searches; an empty result means the spelling differs.

Instructions

Look up a brand by its Persian name: filter code and brand page.

Pass brand_code in brand_codes of tl_search / tl_find_cheapest / tl_category_products, or brand_page as the url of tl_category_products. Empty list: the site spells the brand differently (هوآوی, not هواوی); take the code from the brands facet of tl_search.

Input Schema

NameRequiredDescriptionDefault
nameYesPersian brand name, e.g. 'سامسونگ'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • changedInput schema / properties / name / description
      Previous value: -"Brand name in Persian as written on the site, e.g. 'سامسونگ' or 'لنوو'."New value: +"Persian brand name, e.g. 'سامسونگ'."
    • removedInput schema / properties / name / title
      Removed value: -"Name"
    • removedInput schema / title
      Removed value: -"tl_find_brandArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "tl_find_brandDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.5/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, openWorld, non-destructive), but the description adds non-obvious behavior: an empty list means a spelling mismatch (هوآوی vs هواوی) rather than a missing brand. That failure-mode disclosure is genuinely useful and not derivable from the annotations.

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?

Four short lines, front-loaded with the purpose before the integration and troubleshooting notes. Every line earns its place, though the typographic splitting is slightly more verbose than a single tight paragraph would be.

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 correctly compensates by naming the returned fields (brand_code, brand_page). It is nearly complete; only edge cases such as multiple matches or exact-match requirements go unmentioned.

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% and the schema already gives the type, minLength and an example, so the baseline is 3. The description goes further by warning that the name must match the site's exact Persian spelling, which materially changes how the agent should construct the `name` value.

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+resource ('Look up a brand by its Persian name') and explicitly names the two outputs it yields: a filter code and a brand page. This distinguishes it from all siblings, which consume those outputs rather than produce them.

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 routes the outputs: 'Pass brand_code in brand_codes of tl_search / tl_find_cheapest / tl_category_products, or brand_page as the url of tl_category_products.' It also provides a fallback path (the `brands` facet of tl_search) when this tool returns nothing, so the agent knows both when to use it and what to do when it fails.

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