Skip to main content
Glama

Search products

kh_search
Read-onlyIdempotent

Search Khanoumi's cosmetics, skin and hair care, and perfume catalog by keyword to retrieve matching products' price, discount, stock, category IDs, and brand slugs.

Instructions

Search products by keyword: price, discount and stock of each match, plus matching category ids and brand slugs.

Use first for "price of X". Next: kh_find_cheapest, kh_browse, kh_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": {
      "query": "<query>"
    },
    "name": "kh_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoFrom 1.
sortNoBy payable price for cheapest / most_expensive.popular
limitNoProducts per page.
queryYesPersian or English keyword, e.g. 'کرم مرطوب کننده', 'cerave'.
max_priceNoMax payable price, Toman.
min_priceNoMin payable price, Toman.
in_stock_onlyNoOnly orderable products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.4.0
    • changedInput schema / properties / in_stock_only / description
      Previous value: -"Only products that can be ordered now."New value: +"Only orderable products."
    • changedInput schema / properties / limit / description
      Previous value: -"Products per page (sponsored items are left out)."New value: +"Products per page."
    • removedInput schema / properties / max_price / anyOf
      Removed value: -[
      -  {
      -    "minimum": 1,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / max_price / description
      Previous value: -"Maximum payable price in Toman, e.g. 1500000."New value: +"Max payable price, Toman."
    • addedInput schema / properties / max_price / minimum
      Added value: +1
    • addedInput schema / properties / max_price / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedInput schema / properties / min_price / anyOf
      Removed value: -[
      -  {
      -    "minimum": 0,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / min_price / description
      Previous value: -"Minimum payable price in Toman, e.g. 500000."New value: +"Min payable price, Toman."
    • addedInput schema / properties / min_price / minimum
      Added value: +0
    • addedInput schema / properties / min_price / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • changedInput schema / properties / page / description
      Previous value: -"Page number, from 1."New value: +"From 1."
    • changedInput schema / properties / query / description
      Previous value: -"Product name or keyword, Persian or English, e.g. 'کرم مرطوب کننده' or 'cerave'."New value: +"Persian or English keyword, e.g. 'کرم مرطوب کننده', 'cerave'."
    • changedInput schema / properties / sort / description
      Previous value: -"popular = site default; cheapest / most_expensive by payable price."New value: +"By payable price for cheapest / most_expensive."
  2. Changed10 schema fields changedv0.2.0
    • removedInput schema / properties / in_stock_only / title
      Removed value: -"In Stock Only"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / max_price / title
      Removed value: -"Max Price"
    • removedInput schema / properties / min_price / title
      Removed value: -"Min Price"
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • changedInput schema / properties / sort / description
      Previous value: -"Order: popular (the site's default, most visited), cheapest / most_expensive (payable price), newest."New value: +"popular = site default; cheapest / most_expensive by payable price."
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"kh_searchArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "kh_searchDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered; the description's added value is disclosing what comes back per match (price, discount, stock) plus category ids and brand slugs. With no output schema, that return-shape disclosure is genuinely useful. It does not discuss result caps or empty-match behavior, keeping it short of 5.

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 compact sentences with zero filler, and the routing information is front-loaded right after the purpose statement. Nothing in it is redundant with the schema or annotations.

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?

For a 7-parameter, fully-described search schema with rich annotations, the description covers purpose, return contents, and sibling routing adequately. Minor gaps remain: no mention of whether total result counts or pagination metadata are returned, which matters since there is no output 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%, including units (Toman), enum meanings for sort, and the Persian/English keyword example, so the schema carries parameter semantics fully. The description adds no syntax or constraint detail beyond that, which is the baseline-3 case.

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?

The description gives a specific verb and resource ('Search products by keyword') and goes further by naming the payload (price, discount, stock, category ids, brand slugs), so an agent knows both action and result shape. It falls short of 5 because the boundary versus keyword-less siblings like kh_browse is only implied by the routing line, not stated as a distinction.

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?

It gives an explicit priority ('Use first for "price of X"') and names the alternatives to try next (kh_find_cheapest, kh_browse, kh_product). What is missing is any when-not guidance or the condition that would make an agent skip straight to a sibling.

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