Skip to main content
Glama
digikala-mcp

digikala-mcp

by sepehr071

Product details and offers

dk_product
Read-onlyIdempotent

Retrieve a product’s price, stock, rating, specs and all seller offers in one call, ordered cheapest first to compare purchase options.

Instructions

Get one product's price, stock, rating, specs and every seller's offer (cheapest first).

An offer is one color/size from one seller; stock_left only when low; ships_by 'jet' = same-day Tehran/Karaj. lowest_price_30d can be a one-day dip (dk_price_history's lowest_2_days is steadier).

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": {
      "product_id": "<product_id>"
    },
    "name": "dk_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_offersNo
product_idYes
include_specsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.6.0
    • removedInput schema / properties / include_specs / description
      Removed value: -"Include the specification table."
    • removedInput schema / properties / max_offers / description
      Removed value: -"Max seller offers to return, cheapest first."
    • removedInput schema / properties / product_id / description
      Removed value: -"Digikala product id, the number in 'dkp-<id>' (from dk_search etc.), e.g. 20109389."
  2. Changed5 schema fields changedv0.4.0
    • removedInput schema / properties / include_specs / title
      Removed value: -"Include Specs"
    • removedInput schema / properties / max_offers / title
      Removed value: -"Max Offers"
    • removedInput schema / properties / product_id / title
      Removed value: -"Product Id"
    • removedInput schema / title
      Removed value: -"dk_productArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dk_productDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare this a safe, idempotent, read-only lookup, so the description is free to spend its words on payload semantics instead. It does that well: it defines what an offer is ('one color/size from one seller'), that stock_left appears only when low, that ships_by 'jet' means same-day Tehran/Karaj, and that lowest_price_30d may be a one-day dip.

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?

Two sentences, both load-bearing: the first states what is returned and in what order, the second disambiguates the returned fields and the sibling metric. Nothing is repeated from the title and the most important scoping fact leads.

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?

With no output schema, the description correctly carries the burden of explaining the returned fields and their caveats, which it does in detail. The remaining gap is parameter-level guidance (offer cap, specs toggle), which an agent would want before choosing argument values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions product_id, max_offers (default 15, cap 50) or include_specs. The only tacit signal is that 'specs' is part of the result, which hints at include_specs without explaining it, leaving the caller to infer the meaning and bounds of all three parameters from the schema alone.

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 verb and resource ('Get one product's price, stock, rating, specs and every seller's offer') and pins the scope to a single product with offers ordered cheapest-first. That clearly separates it from sibling aggregate tools like dk_search, dk_compare and dk_price_history.

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 routing cue to dk_price_history for steadier lowest-price data, which tells the agent when to prefer the sibling metric. It does not, however, spell out the precondition for calling this tool at all (having a product_id, e.g. from dk_search), so guidance is clear in context but not exhaustive.

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