Skip to main content
Glama
sepehr071

digikala-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Product questions and answers

dk_questions
Read-onlyIdempotent

Read customer questions and answers for a Digikala product to resolve doubts on compatibility, size, or registration before buying.

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). Use for practical doubts (compatibility, size, registration).

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1 (20 products per page).
sortNoOrder of the questions.most_answered
full_textNoSkip text cuts and pros/cons caps; return everything whole.
product_idYesDigikala product id, the number in 'dkp-<id>' (from dk_search etc.), e.g. 20109389.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the safe-read profile (readOnly, idempotent, non-destructive), and the description adds real behavior beyond that: 20 items per page and texts truncated to 300 characters unless full_text=true. It does not mention rate limits or total counts, but this is solid added context.

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?

Two compact sentences with the core read/count facts front-loaded and the use case trailing. No filler, though the truncation detail is packed into a parenthetical that is slightly dense.

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 read-only, single-object listing tool with a fully documented schema and annotations covering safety, this is nearly complete. The absence of an output schema is not an issue since the description conveys the return shape (questions, answers, truncation).

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%, so baseline is 3. The description restates full_text's effect and page size, which the schema already documents, so it adds little beyond the structured fields.

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?

States a specific verb and resource: 'Read customers' questions' with the answer cardinality made concrete ('up to 2 answers each'). It is clearly a Q&A reader, distinguishable in spirit from dk_reviews, though it never names that nearest sibling explicitly.

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?

'Use for practical doubts (compatibility, size, registration)' gives concrete when-to-use context. It does not state when NOT to use it or point to alternatives like dk_reviews, so it stops short of full routing guidance.

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