Skip to main content
Glama
digikala-mcp

digikala-mcp

by sepehr071

Re-check a shortlist

dk_shortlist
Read-onlyIdempotent

Re-price up to 10 Digikala products in one call, returning current price, seller offers, stock, rating, and 30-day price low for quick comparison and discount checks.

Instructions

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

low_30d is the lowest price held two days in a row, vs_30d_low_pct today's price above it.

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_ids": "<product_ids>"
    },
    "name": "dk_shortlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idsYese.g. [20109389, 20110013].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / product_ids / description
      Previous value: -"1-10 product ids, e.g. [20109389, 20110013]."New value: +"e.g. [20109389, 20110013]."
  2. 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
  3. Addedv0.2.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior. The description adds useful behavioral context by naming returned fields, giving the Toman unit, and defining low_30d and vs_30d_low_pct, though it does not describe error handling or missing-product behavior.

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 two tight sentences, front-loaded with the action and scope. The second sentence only defines fields that need clarification, with no filler or 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 simple one-parameter read-only batch tool with no output schema, the description gives enough to call it correctly and understand the main returned fields. Minor gaps remain around exact return structure and failure cases, but nothing critical is missing for 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%, and the single product_ids parameter is fully documented with type, min/max items, and an example. The description's 'up to 10 products' mirrors the schema constraint and adds little beyond it, so baseline 3 is appropriate.

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 scope: re-pricing up to 10 products in one call, and lists the returned fields. It clearly identifies a batch re-check operation, but it does not explicitly name a sibling tool or contrast itself with single-product tools like dk_product or dk_compare.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The title 'Re-check a shortlist' and the 'up to 10 products in one call' wording imply the intended use case. However, there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance, so the agent must infer fit from context.

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