Skip to main content
Glama
sepehr071

khanoumi-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search products

kh_search
Read-onlyIdempotent

Search Khanoumi's cosmetics catalog by keyword to retrieve product prices, discounts, stock, and matching categories and brands.

Instructions

Search products by keyword: price, discount and stock of each match. Also returns the best-matching categories (ids for kh_browse) and brands (slugs).

Use first for "price of X". Next: kh_find_cheapest, kh_filters + kh_browse, kh_product.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1.
sortNopopular = site default; cheapest / most_expensive by payable price.popular
limitNoProducts per page (sponsored items are left out).
queryYesProduct name or keyword, Persian or English, e.g. 'کرم مرطوب کننده' or 'cerave'.
max_priceNoMaximum payable price in Toman, e.g. 1500000.
min_priceNoMinimum payable price in Toman, e.g. 500000.
in_stock_onlyNoOnly products that can be ordered now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds non-obvious behavioral value: the response includes best-matching categories and brands beyond the product list, which tells the agent to expect auxiliary result sets. It does not discuss pagination or result-count behavior, but the schema covers paging.

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 tight paragraphs: the first states purpose and return shape, the second is a compact routing line. Nothing is redundant and the primary use case is front-loaded.

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 7 parameters, no output schema and rich annotations, the description covers purpose, return fields and sibling routing adequately. It could say slightly more about how many categories/brands come back or how paging interacts with the auxiliary results, but nothing critical for invocation is missing.

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 and defaults, so the schema carries the parameter burden. The description adds nothing about individual parameters beyond restating that price/discount/stock are returned, so the baseline 3 applies.

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 (search products by keyword) and immediately enumerates what each match carries (price, discount, stock) plus the secondary payload (category ids, brand slugs). An agent can distinguish this from kh_product, kh_browse and kh_find_cheapest 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an explicit entry-point rule ('Use first for "price of X"') and names the follow-up alternatives (kh_find_cheapest, kh_filters + kh_browse, kh_product) in an implied order. It stops short of stating when each alternative is preferred over this one, so the routing is directional but not fully specified.

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