Skip to main content
Glama
digikala-mcp

digikala-mcp

by sepehr071

Product questions and answers

dk_questions
Read-onlyIdempotent

Retrieves a product's customer questions with up to two answers each, paginated 20 per page; set full_text to avoid 300-character text cuts.

Instructions

Read customers' questions (20 per page) with up to 2 answers each (answered_by: buyer, seller, ...).

Texts are cut to 300 characters (full_text=true: whole).

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_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNomost_answered
full_textNoNo text cuts.
product_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.6.0
    • changedInput schema / properties / full_text / description
      Previous value: -"Skip text cuts and pros/cons caps; return everything whole."New value: +"No text cuts."
    • removedInput schema / properties / page / description
      Removed value: -"Page number, from 1 (20 products per page)."
    • removedInput schema / properties / product_id / description
      Removed value: -"Digikala product id, the number in 'dkp-<id>' (from dk_search etc.), e.g. 20109389."
    • removedInput schema / properties / sort / description
      Removed value: -"Order of the questions."
  2. Changed6 schema fields changedv0.4.0
    • addedInput schema / properties / full_text
      Added value: +{
      +  "default": false,
      +  "description": "Skip text cuts and pros/cons caps; return everything whole.",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / product_id / title
      Removed value: -"Product Id"
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"dk_questionsArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dk_questionsDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnly, non-destructive, idempotent and open-world behavior, so the description adds genuinely new operational detail: 20 items per page, a cap of 2 answers per question, the answered_by attribution, and a 300-character truncation that full_text lifts. It still does not mention the page ceiling (100) or what happens with out-of-range pages.

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 short sentences, zero filler, with the core behavior (pagination size and answer cap) front-loaded and the text-truncation caveat immediately after.

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 4-parameter read tool with full annotation coverage and no output schema, the description gives the agent enough to call it correctly: item granularity, page contents, and truncation behavior. Remaining gaps are minor, mainly sort/ordering effects and page-boundary handling.

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 only 25% (just full_text), so the description must compensate and it partly does: it explains the 300-character cut and what full_text=true yields, plus the implicit 20-per-page meaning of page. It says nothing about sort semantics ('newest' vs 'most_answered') or product_id, so the compensation is incomplete.

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: reading customers' questions for a product, with up to 2 answers each. That is clearly distinct from dk_reviews and the sibling search tools, though it does not name a sibling explicitly to route the agent.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative (e.g., dk_reviews for ratings, dk_product for the item itself). Usage is only inferable from the resource name.

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