khanoumi-mcp

Overview Schema Source Related Servers Discussions Admin

Browse a category, brand or tag

kh_browse

Read-onlyIdempotent

Browse products by category, brand, or campaign tag, then sort by price or newest and filter by attributes and price range to find matching cosmetics, skincare, or perfume items.

Instructions

List the products of a category, brand(s) or campaign tag with sorting, price range and filters.

Use for "cheapest CeraVe moisturizer", "sunscreens for oily skin under 800,000 Toman", "newest Golden Rose lipsticks", "everything in today's pink box". Pass at least one of category_id (kh_categories), brands (kh_brands) or tag (kh_deals). Filter ids (brands, colors, skin / hair type, free-from, ingredient facets) and the price range come from kh_filters. There is no rating or discount sort: check candidates with kh_product / kh_reviews. Details: kh_product.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tag`	No	Collection / campaign tag slug from kh_deals (the part after /tags/), e.g. 'festival-js' (pink box).
`page`	No	Page number, from 1.
`sort`	No	Order: popular (the site's default, most visited), cheapest / most_expensive (payable price), newest.	popular
`limit`	No	Products per page (sponsored items are left out).
`query`	No	Optional keyword inside the listing.
`brands`	No	Brand slugs from kh_brands / kh_filters (OR), e.g. ['simple', 'cerave'].
`colors`	No	Color ids from kh_filters (OR), e.g. ['3'] (red).
`facets`	No	Attribute filter keys from kh_filters, all must match (AND), e.g. ['facetKey.skin-type:oily'].
`max_price`	No	Maximum payable price in Toman, e.g. 1500000.
`min_price`	No	Minimum payable price in Toman, e.g. 500000.
`category_id`	No	Category id from kh_categories or kh_search, e.g. 145 (moisturizers).
`in_stock_only`	No	Only products that can be ordered now.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 6, 2026

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, openWorld, non-destructive), so the description earns credit for adding real behavioral limits: no rating or discount sort exists, and results should be verified via kh_product / kh_reviews. It stops short of describing pagination or result-cap behavior, which a browse tool would benefit from.

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?

Front-loaded purpose followed by example queries, then constraints and pointers to sibling tools. Dense but every sentence carries information; the quoted example phrasings are slightly verbose but useful for query matching.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain return values, and it instead covers the things an agent can't infer: the at-least-one-selector rule, filter provenance, sorting limits, and where to go for verification. Nothing essential is missing for a 12-param read 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, but the description adds a genuine constraint not expressed in the schema: at least one of category_id, brands or tag must be supplied even though none are marked required. It also clarifies where each filter id must be sourced (kh_filters, kh_deals, kh_categories).

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?

Opens with a specific verb+resource+scope: 'List the products of a category, brand(s) or campaign tag with sorting, price range and filters.' The concrete example queries ('cheapest CeraVe moisturizer', 'sunscreens for oily skin under 800,000 Toman') make the tool's domain unmistakable against siblings like kh_search or kh_product.

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 states the invocation constraint ('Pass at least one of category_id, brands or tag'), names the upstream lookup tools (kh_categories, kh_brands, kh_deals, kh_filters), and rules out alternatives by noting there is no rating or discount sort and directing candidates to kh_product / kh_reviews.

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

Deploy Server