Skip to main content
Glama
sepehr071

khanoumi-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Product details

kh_product
Read-onlyIdempotent

Retrieve one product's full details, including Toman price, discount, shade, size and seller variants with stock, max quantity, rating, brand, categories, attributes and description.

Instructions

Get one product's full record: price and discount (Toman), every shade / size / seller variant with its own price, stock and max quantity, rating, brand, categories, attributes and description.

Use after kh_search / kh_browse, or to check that a shade is in stock and its price. Next: kh_reviews, kh_similar, kh_store_info (fees).

Input Schema

NameRequiredDescriptionDefault
productYesSlug from kh_search / kh_browse (e.g. 'golden-rose-sheer-bright-lipstick-112222') or numeric id.
full_textNoDo not clip description and how_to_use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.0
    • addedInput schema / properties / full_text
      Added value: +{
+  "default": false,
+  "description": "Do not clip description and how_to_use.",
+  "type": "boolean"
+}
    • 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_productArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "kh_productDictOutput",
-  "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 declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the shape and richness of the payload (per-variant pricing, stock, max quantity, currency in Toman), which tells the agent this is a heavyweight detail fetch rather than a summary. It stops short of noting response size or rate limits, so not a 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 sentences, no filler. The record contents are front-loaded and the second sentence is a compact routing cue (predecessor tools, then next tools). Every clause carries information.

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 no output schema, the description takes on the burden of explaining return values and does so comprehensively, plus it supplies the workflow context. For a two-parameter read tool, nothing an agent needs to call it correctly 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%, so both parameters ('product' with its slug/numeric-id format and 'full_text' clipboard behavior) are already fully documented in the schema. The description adds no additional parameter semantics, making the baseline 3 correct.

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 ('Get one product's full record') and enumerates the returned record (price/discount in Toman, per-variant price/stock/max quantity, rating, brand, categories, attributes, description). The 'one product' framing cleanly distinguishes it from list-oriented siblings like kh_search and kh_browse.

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 places the tool in a workflow: 'Use after kh_search / kh_browse, or to check that a shade is in stock and its price', and names the natural continuations (kh_reviews, kh_similar, kh_store_info with a parenthetical on fees). Both the entry condition and the next step are given.

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