Skip to main content
Glama
digikala-mcp

digikala-mcp

by sepehr071

Find cheapest product

dk_find_cheapest
Read-onlyIdempotent

Find in-stock products matching a query, excluding accessories and sorted by price from low to high in Toman.

Instructions

Find the cheapest in-stock products that really match a query, sorted by price (Toman).

Keeps titles with every query word and drops accessories. Then dk_product on the winner: another seller may be cheaper.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "dk_find_cheapest"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
pagesNoRelevance pages to scan.
queryYesPersian or English words, e.g. 'گوشی سامسونگ'.
max_priceNo
min_priceNoToman. Default: 1/4 of the top matches' median price (drops accessories).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.6.0
    • removedInput schema / properties / limit / description
      Removed value: -"Max products to return."
    • removedInput schema / properties / max_price / anyOf
      Removed value: -[
      -  {
      -    "minimum": 0,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / max_price / description
      Removed value: -"Highest price in Toman, e.g. 50000000."
    • addedInput schema / properties / max_price / minimum
      Added value: +0
    • addedInput schema / properties / max_price / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • removedInput schema / properties / min_price / anyOf
      Removed value: -[
      -  {
      -    "minimum": 0,
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / min_price / description
      Previous value: -"Skip anything cheaper than this, in Toman. Default: a quarter of the median price of the top matches (ignoring max_price), which drops accessories."New value: +"Toman. Default: 1/4 of the top matches' median price (drops accessories)."
    • addedInput schema / properties / min_price / minimum
      Added value: +0
    • addedInput schema / properties / min_price / type
      Added value: +[
      +  "integer",
      +  "null"
      +]
    • changedInput schema / properties / pages / description
      Previous value: -"Relevance pages to scan, 20 products each."New value: +"Relevance pages to scan."
    • changedInput schema / properties / query / description
      Previous value: -"Product name or words, Persian or English, e.g. 'گوشی سامسونگ' or 'airpods pro'."New value: +"Persian or English words, e.g. 'گوشی سامسونگ'."
  2. Changed8 schema fields changedv0.4.0
    • changedInput schema / properties / limit / default
      Previous value: -20New value: +10
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / max_price / title
      Removed value: -"Max Price"
    • removedInput schema / properties / min_price / title
      Removed value: -"Min Price"
    • removedInput schema / properties / pages / title
      Removed value: -"Pages"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"dk_find_cheapestArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dk_find_cheapestDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the read-only, idempotent, non-destructive annotations, the description explains filtering behavior: it keeps titles containing every query word, drops accessories, and returns in-stock items sorted by price. It does not discuss pagination, result size, or rate limits, but it adds meaningful behavioral context.

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?

The description is short and front-loaded with the core action, then adds filtering behavior and a useful next step. Every sentence contributes information without repetition.

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?

For a five-parameter search tool without an output schema, the description covers the core purpose, matching behavior, sorting, and a follow-up workflow. It is missing some invocation details, such as how pages and limit shape the scan, and does not describe the returned product shape.

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 coverage is 60%, and the description adds some query-matching semantics and price-currency context. However, it does not clarify limit, pages, max_price, or how min_price interacts with the accessory-dropping behavior beyond what the schema already provides.

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 states a specific action and resource: find the cheapest in-stock products matching a query, sorted by price in Toman. It also distinguishes the result from a direct product lookup by pointing to dk_product for seller comparison.

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 clearly implies when to use the tool: when the agent wants the cheapest in-stock match for a query. It also provides a useful follow-up path via dk_product, though it does not explicitly compare itself with alternatives such as dk_best_for_budget or dk_search.

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