Skip to main content
Glama
sepehr071

khanoumi-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Current deals and discount codes

kh_deals
Read-onlyIdempotent

List today's home-page deals, including the daily pink box, biggest discount first, plus the current pop-up campaign's public discount code.

Instructions

List today's home-page deals (daily pink box "جعبه صورتی" and other rows), biggest discount first, plus the public discount code of the current pop-up campaign.

Use for "what's on sale". pink_box_ends_in_seconds = time left in the daily box. A section's tag lists all its products via kh_browse(tag=...); a section without a tag has only link. Voucher conditions are in voucher.text.

Input Schema

NameRequiredDescriptionDefault
limitNoMax deals to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • changedInput schema / properties / limit / default
      Previous value: -30New value: +10
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / title
      Removed value: -"kh_dealsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "kh_dealsDictOutput",
-  "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 readOnly/openWorld/idempotent/non-destructive, so safety is covered. The description adds real behavioral context beyond that: results are ordered 'biggest discount first', sections may have a `tag` (full product list) or only a `link`, and voucher conditions live in voucher.text. It does not discuss auth or rate limits, but the ordering and field-structure disclosure are substantive.

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?

Front-loaded with the core purpose, then dense but useful field notes in a compact second sentence. No filler sentences; every clause (pink_box_ends_in_seconds, tag vs link, voucher.text) 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 must explain return shape, and it does so by naming the key response fields (pink_box_ends_in_seconds, tag/link, voucher.text) and their meaning. It is close to complete, though it doesn't describe the overall response envelope or campaign-code placement explicitly.

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?

There is a single optional `limit` parameter with 100% schema description coverage, so the schema fully documents it. The description adds nothing about the limit or pagination, which is the correct baseline 3 when the schema does the heavy lifting.

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?

The description names a specific verb and resource ('List today's home-page deals … plus the public discount code of the current pop-up campaign'), and states scope (today's home-page rows, biggest discount first). An agent can distinguish this from kh_search or kh_find_cheapest without opening another 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?

It gives an explicit usage cue ('Use for "what's on sale"') and cross-links to the sibling kh_browse for section tag expansion. It stops short of stating when to prefer kh_find_cheapest or kh_search over this tool, so there is no explicit exclusion.

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