Skip to main content
Glama
sepehr071

masterkala-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Find cheapest product

mk_find_cheapest
Read-only

Find the cheapest in-stock products for a keyword in MasterKala's catalog, returning a flat list sorted by final payable price.

Instructions

Find the cheapest in-stock products for a keyword, one flat list sorted by payable price.

Use when the user wants the lowest price for X: scans the results, keeps items buyable online now, sorts by final_price. free_shipping = basket reaches 5,000,000 Toman (bulky items never); exact fee and date: mk_shipping. complete=false: in-stock items go past scanned, raise scan.

Input Schema

NameRequiredDescriptionDefault
scanNoMax search results to scan, 500 per request; stops early once the in-stock items end.
limitNoMax offers to return.
queryYesProduct name or keyword, Persian or English, e.g. 'هندزفری بلوتوث' or 'xiaomi'.
match_all_wordsNoKeep only titles that contain every word of the query.
include_accessoriesNoAlso keep cases, covers, screen protectors and straps made for the product (dropped by default unless the query names them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.3.0
    • removedInput schema / properties / include_accessories / title
      Removed value: -"Include Accessories"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / match_all_words / title
      Removed value: -"Match All Words"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / scan / title
      Removed value: -"Scan"
    • removedInput schema / title
      Removed value: -"mk_find_cheapestArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mk_find_cheapestDictOutput",
-  "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 only declare readOnlyHint=true, so the description carries the rest: it discloses the free-shipping threshold (5,000,000 Toman), the bulky-item exception, and the early-stop/`complete=false` scanning behavior with a remedy ('raise scan'). That is meaningful behavioral context beyond the annotation, though return format details remain unstated.

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 with the core purpose and usage in the first two lines, then dense terse fragments for edge rules. Efficient, though the telegraphic 'complete=false: ... raise scan' phrasing is slightly compressed at the cost of readability.

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 fortunately explains key return semantics (flat list, payable-price sort, complete flag, scanned boundary) and the shipping caveat. A short note on result fields or pagination would make it fully complete.

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 real value by tying the `scan` parameter to output behavior ('in-stock items go past scanned, raise scan') and clarifying that free_shipping for bulky items behaves differently. It goes beyond restating the schema.

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 precise verb+resource+scope: cheapest in-stock products for a keyword, returned as one flat list sorted by payable price. This clearly distinguishes it from siblings like mk_search or mk_deals, which do not promise price-sorted stock filtering.

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 'Use when the user wants the lowest price for X' and names an alternative destination for adjacent needs (exact fee and date -> mk_shipping). The agent can route correctly without opening any schema.

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