masterkala-mcp

Overview Schema Source Related Servers Discussions Admin

Find cheapest product

mk_find_cheapest

Read-onlyIdempotent

Find in-stock products for a keyword, sorted by final price after discounts. Use when you need to find a budget-friendly option.

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 search results, keeps items that can be bought online now, and sorts by final_price (after discount, Toman). Most items ship free when the basket reaches 5,000,000 Toman (free_shipping); bulky ones never do. mk_shipping gives the exact fee and date. complete=false means in-stock items go on past scanned: raise scan.

Input Schema

TableJSON Schema

Name	Required	Description
`scan`	No	Max search results to scan, 500 per request; stops early once the in-stock items end.
`limit`	No	Max offers to return.
`query`	Yes	Product name or keyword, Persian or English, e.g. 'هندزفری بلوتوث' or 'xiaomi'.
`match_all_words`	No	Keep only titles that contain every word of the query.
`include_accessories`	No	Also keep cases, covers, screen protectors and straps made for the product (dropped by default unless the query names them).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only cover the safety profile (read-only, idempotent, non-destructive); the description adds substantial behavior beyond them: it scans search results and stops early, filters to online-purchasable items, sorts by final_price after discount in Toman, explains the free-shipping threshold and bulky-item exception, and interprets complete=false as a signal to raise `scan`.

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, then usage trigger, then mechanics; every sentence adds information about scanning, sorting, or shipping. Slightly long but no waste.

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?

An output schema exists so return shape need not be explained, yet the description still clarifies the one return value an agent must act on (complete=false) plus pricing and shipping semantics. Combined with the named mk_shipping alternative, nothing needed to call this correctly is missing.

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 already 100%, so the baseline is 3. The description earns an extra point by linking the output flag to the `scan` parameter ('complete=false ... raise scan') and by defining the sort key (final_price, after discount, Toman), which the schema does not state.

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 (find) plus resource and a tight qualifier ('cheapest in-stock products for a keyword'), and the sorting key ('payable price') makes it immediately distinguishable from generic siblings like mk_search or mk_deals without opening any 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?

Gives an explicit trigger ('Use when the user wants the lowest price for X') and routes the shipping-fee question to mk_shipping, which is a genuine alternative. It stops short of naming when NOT to use it (e.g. broad browsing vs. exact-price comparison), so it is clear but not exhaustive.

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

Deploy Server