Skip to main content
Glama
sepehr071

digikala-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Similar products

dk_similar
Read-onlyIdempotent

Find products similar to a Digikala item by product ID, including other models and brands. Sort results by price to find cheaper alternatives and compare offers.

Instructions

List products similar to one (same kind, other models and brands).

sort='cheapest' gives cheaper alternatives; then dk_compare.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1 (20 products per page).
sortNoOrder of the results.relevance
product_idYesDigikala product id, the number in 'dkp-<id>' (from dk_search etc.), e.g. 20109389.
in_stock_onlyNoOnly products that can be bought now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.4.0
    • removedInput schema / properties / in_stock_only / title
      Removed value: -"In Stock Only"
    • 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_similarArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "dk_similarDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish this as a safe, idempotent, read-only, open-world lookup, so the safety profile is covered. The description adds useful behavioral context — the notion of similarity and that one sort mode yields cheaper alternatives — but says nothing about return shape, result size, or pagination behavior beyond what the schema states.

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 short sentences, front-loaded with the purpose before the parameter hint and next-step pointer. The trailing fragment "then dk_compare." is terse almost to the point of ambiguity, but no sentence is wasted.

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 listing tool whose 4 parameters are fully documented in the schema, the description covers purpose, similarity scope, a key sort semantic, and the natural follow-up call. The main remaining gap is that, with no output schema, it never characterizes what a result entry contains.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning the schema lacks: the schema only says 'Order of the results' for sort, while the description explains that sort='cheapest' resolves to cheaper alternatives relative to the source product. This only covers one of eight enum values, so it is above baseline but not exhaustive.

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 gives a specific verb+resource ("List products similar to one") and immediately defines what 'similar' means — same kind, other models and brands — which disambiguates it from generic listing siblings like dk_search or dk_category_products. It stops short of explicitly naming a sibling it should not be used in place of.

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 concrete usage direction: use sort='cheapest' to surface cheaper alternatives, and it names the follow-up tool (dk_compare) as a chained next step. There is no 'when not to use this' guidance or comparison against the other discovery tools, so it is clear context rather than full routing.

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