Skip to main content
Glama
sepehr071

digikala-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Find cheapest product

dk_find_cheapest
Read-onlyIdempotent

Find in-stock Digikala products sorted by price in Toman (low to high), filtering out accessories, to identify affordable matches for a query. Use it for budget product searches such as “cheap X”.

Instructions

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

Scans the top relevant results, keeps titles with every query word (else any word, with a note) and drops accessories. Use for "cheapest X"; then dk_product on the winner, as another seller may sell it for less.

Input Schema

NameRequiredDescriptionDefault
limitNoMax products to return.
pagesNoRelevance pages to scan, 20 products each.
queryYesProduct name or words, Persian or English, e.g. 'گوشی سامسونگ' or 'airpods pro'.
max_priceNoHighest price in Toman, e.g. 50000000.
min_priceNoSkip anything cheaper than this, in Toman. Default: a quarter of the median price of the top matches (ignoring max_price), which drops accessories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. First observedv0.1.0

TDQS

A3.9/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 detail beyond that: it scans the top relevant results, keeps titles containing every query word (falling back to any word with a `note`), and drops accessories. That matching-relaxation behavior is exactly the kind of thing an agent cannot infer from annotations or schema.

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?

Three compact sentences, front-loaded with purpose then matching logic then routing; nothing is filler. The mid-sentence line break before the backticked `note` makes the structure slightly choppier than ideal, keeping it just under a 5.

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 5-parameter, no-output-schema lookup tool, the description covers purpose, filtering behavior, ordering, unit (Toman), and the next step. Return shape is only hinted at via the mention of a `note`, which is a minor gap but not a blocker for correct invocation.

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 the schema already documents limit, pages, query, min_price, and max_price including the accessory-dropping default. The description's 'drops accessories' reiterates the schema's min_price note rather than adding new parameter meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource with scope: 'Find the cheapest in-stock products that really match a query, sorted by price.' It also signals the intended phrasing ('Use for "cheapest X"'), which separates it from generic siblings like dk_search. It stops short of distinguishing itself from the closest sibling, dk_best_for_budget, so it is clear but not fully sibling-differentiated.

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 a concrete when-to-use trigger ('cheapest X') and a follow-up step ('then dk_product on the winner, as another seller may sell it for less'). There is no explicit when-not or named alternative for budget-style queries, so it is clear context without exclusions.

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