Skip to main content
Glama
sepehr071

khanoumi-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Similar and complementary products

kh_similar
Read-onlyIdempotent

Find alternatives to a product or complementary items with prices and stock. Use when a product is out of stock or too expensive, or to build a routine.

Instructions

List alternatives to a product (about 20) or the products the shop pairs with it, with prices and stock.

Use when a product is out of stock or too expensive, or to build a routine.

Input Schema

NameRequiredDescriptionDefault
kindNosimilar = alternatives; complementary = products the shop pairs with it (often empty).similar
productYesSlug from kh_search / kh_browse (e.g. 'golden-rose-sheer-bright-lipstick-112222') or numeric id.
in_stock_onlyNoOnly products that can be ordered now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.2.0
    • removedInput schema / properties / in_stock_only / title
      Removed value: -"In Stock Only"
    • changedInput schema / properties / kind / description
      Previous value: -"similar = alternatives to this product; complementary = products the shop pairs with it (routine)."New value: +"similar = alternatives; complementary = products the shop pairs with it (often empty)."
    • removedInput schema / properties / kind / title
      Removed value: -"Kind"
    • changedInput schema / properties / product / description
      Previous value: -"Product slug from kh_search / kh_browse (e.g. 'golden-rose-sheer-bright-lipstick-112222') or the numeric product id (e.g. '112222')."New value: +"Slug from kh_search / kh_browse (e.g. 'golden-rose-sheer-bright-lipstick-112222') or numeric id."
    • removedInput schema / properties / product / title
      Removed value: -"Product"
    • removedInput schema / title
      Removed value: -"kh_similarArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "kh_similarDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile needs no restating. The description adds return context ('with prices and stock') and an item count, but does not disclose pagination, whether results are ranked, or that complementary lists are frequently empty (that fact is left to the schema). Modest added value against an already-covered annotation set.

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 sentences, front-loaded with what is returned and followed by the routing condition. No filler or repetition of the title; every clause carries information.

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 supplies the essential return shape (products with prices and stock, roughly 20 items) and the selection rationale. It covers enough to call correctly, though it omits pagination/ordering behavior and the near-empty nature of complementary results.

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%: kind, product slug format, and in_stock_only are all documented in the schema with examples. The description adds no parameter syntax or format detail beyond that, so the baseline 3 is correct.

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 ('List') and resource ('alternatives to a product... or the products the shop pairs with it'), explicitly disambiguating the two modes the `kind` enum offers, plus a concrete count ('about 20'). It stops short of naming sibling tools like kh_product, so an agent gets the resource but no direct routing cue.

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?

Gives explicit when-to-use triggers ('when a product is out of stock or too expensive, or to build a routine'), which is strong context. It does not state when-not to use it or point to a competing sibling such as kh_product or kh_find_cheapest, so it lacks the exclusions a 5 would need.

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