Skip to main content
Glama
sepehr071

digikala-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Seller profile and products

dk_seller
Read-onlyIdempotent

Check a Digikala seller's reputation and products before recommending them. See rating, on-time shipping, cancellations, returns, and stock.

Instructions

Get a seller's reputation (rating 0-5, on-time shipping, cancellations, returns) and products.

Use before recommending an unknown seller. Percentages are the share of good orders (100 = never late).

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1 (20 products per page).
sortNoOrder of the results.best_selling
seller_codeYesSeller code from dk_product offers or a product card, e.g. 'CGDG9'.
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 / seller_code / title
      Removed value: -"Seller Code"
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"dk_sellerArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "dk_sellerDictOutput",
-  "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 declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful metric semantics ('Percentages are the share of good orders, 100 = never late') that annotations cannot express, but says nothing about pagination behavior or how many products come back.

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?

Three tight sentences with zero filler. The purpose and the usage trigger are both front-loaded, and the clarifying note on percentage semantics is placed last where it does not obstruct scanning.

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 does name what is returned (rating, on-time shipping, cancellations, returns, products) and how to interpret the numbers, which is adequate for a read-only lookup. It leaves the 20-products-per-page result shape to the schema, but nothing critical for invoking the tool is missing.

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 every parameter (page, sort, seller_code, in_stock_only) is documented with type, default, enum or pattern in the schema itself. The description only glosses the reputation fields, adding no parameter-level detail beyond the schema, so the baseline 3 applies.

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: fetching a seller's reputation metrics plus their products. It is distinguishable from siblings like dk_best_sellers (listing) and dk_brand_products (brand-scoped), though it never explicitly names those distinctions.

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 before recommending an unknown seller' gives a clear trigger condition for when to reach for this tool. It stops short of stating when not to use it or pointing at an alternative for known/trusted sellers.

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