Skip to main content
Glama
sepehr071

digikala-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Re-check a shortlist

dk_shortlist
Read-onlyIdempotent

Fetch current price, cheapest offer, stock, rating, and 30-day low (Toman) for up to 10 Digikala products in one call to refresh a watchlist or check stock.

Instructions

Re-price up to 10 products in one call: price, cheapest offer, stock, rating and 30-day low (Toman).

Use to refresh a watched list or check stock. cheapest_offer can be below price (the featured offer). low_30d is the lowest price held two days in a row, vs_30d_low_pct today's price above it (0 = at the low); lowest_one_day_30d is Digikala's figure, possibly a one-day dip. For specs use dk_compare; for the daily curve dk_price_history.

Input Schema

NameRequiredDescriptionDefault
product_idsYes1-10 product ids, e.g. [20109389, 20110013].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.0
    • removedInput schema / properties / product_ids / title
      Removed value: -"Product Ids"
    • removedInput schema / title
      Removed value: -"dk_shortlistArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "dk_shortlistDictOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.2.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description goes further and explains non-obvious value semantics: cheapest_offer can sit below price (featured offer), low_30d requires two consecutive days at the low, vs_30d_low_pct is 0 at the low, and lowest_one_day_30d is Digikala's figure that may be a one-day dip. With no output schema, this disambiguation is genuinely load-bearing.

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 capability and its field set are front-loaded in the first sentence, followed by usage, then field semantics. Every remaining sentence defines a term or points at an alternative; nothing is padding.

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?

With no output schema and only one input parameter, the description carries the return-value burden and does exactly that by defining the five fields and their units. An agent knows what it will get back and when to prefer a sibling.

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 100% and the single parameter's description already documents the 1-10 id constraint. The description's 'up to 10 products' merely restates maxItems, adding no new syntax or format meaning, so the baseline 3 applies.

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 and resource ('re-price up to 10 products in one call') and enumerates the returned fields (price, cheapest offer, stock, rating, 30-day low) with currency. It explicitly names the siblings it is not (dk_compare for specs, dk_price_history for the daily curve), so an agent can differentiate without opening another schema.

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?

'Use to refresh a watched list or check stock' gives the triggering scenario, and the closing sentence routes to two concrete alternatives with their selection criteria ('For specs use dk_compare; for the daily curve dk_price_history'). When-to-use and when-not-to-use are both covered.

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