Skip to main content
Glama
sepehr071

digikala-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Best picks for a budget

dk_best_for_budget
Read-onlyIdempotent

Rank in-stock products within a Toman budget by review-weighted rating, so users can find well-rated picks for product searches with a price cap.

Instructions

Rank the best-rated in-stock products within a budget (Toman) by a rating weighted by its count.

A 5.0 from 3 buyers does not beat a 4.6 from 900; ties go to the cheaper one. A query keeps only titles with every word and drops accessories. Use for "best X under Y"; then dk_product, dk_reviews.

Input Schema

NameRequiredDescriptionDefault
limitNoMax picks to return.
pagesNoResult pages to scan, 20 products each.
queryNoWhat to buy, e.g. 'هدفون بی سیم' or 'گوشی سامسونگ'.
max_priceYesBudget in Toman, e.g. 20000000 for 20 million Toman.
min_priceNoSkip anything cheaper, in Toman. Default for a query: a floor that drops accessories.
min_ratingsNoSkip products with fewer ratings than this.
category_codeNoOr a category code instead of a query, e.g. 'mobile-phone' (from dk_suggest).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.4.0
    • removedInput schema / properties / category_code / title
      Removed value: -"Category Code"
    • 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 / min_ratings / title
      Removed value: -"Min Ratings"
    • removedInput schema / properties / pages / title
      Removed value: -"Pages"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"dk_best_for_budgetArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "dk_best_for_budgetDictOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.2.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the bar is lower; the description still adds real behavior: the weighted-rating rule, the tie-breaker, and that queries require every word in the title and drop accessories. It stops short of noting result size or pagination limits of the 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?

Three tight sentences, front-loaded with the purpose, then the ranking rule, then the usage cue. Dense but every sentence carries information; only slight terseness ('Use for "best X under Y"') costs it a point.

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 7-parameter, no-output-schema, open-world tool, the description covers what the tool does to the data (filter, drop accessories, weight ratings) and what to do next. It omits any hint of the returned shape, which is the only notable gap.

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 baseline is 3, but the description adds semantics the schema does not: query matching requires every word in the title and drops accessories, and min_price defaults to a floor that filters accessories when a query is given. That meaningfully clarifies two of the seven parameters.

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 (rank) plus resource (best-rated in-stock products) and the exact ordering key (rating weighted by count, ties to cheaper). This clearly separates it from siblings such as dk_search, dk_best_sellers, and dk_find_cheapest.

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 phrase ('best X under Y') and chains the follow-up tools (dk_product, dk_reviews). It does not, however, state when to prefer this over similar siblings like dk_best_sellers or dk_find_cheapest, so exclusions are missing.

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