Skip to main content
Glama
sepehr071

digikala-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Filter options

dk_filters
Read-onlyIdempotent

List filter options (attributes, colors, sellers, price range, brands) for a Digikala category or search to narrow down products.

Instructions

List the filters of a category or a search: attributes, colors, sellers, price range (Toman), brands.

Attributes give {value title: id}; one with over 15 values only has value_count: call again with attribute_id. Colors are {title: id}; brands {code: id} (category only); categories {code: title} (query only). Pass the ids to dk_category_products or dk_search (attributes={attribute id: [value ids]}, colors, seller_type, brand_ids).

Input Schema

NameRequiredDescriptionDefault
queryNoSearch words instead of a category, e.g. 'هدفون بی سیم'.
brand_codeNoWith category_code: only this brand, e.g. 'samsung'.
attribute_idNoReturn only this attribute with all its values, e.g. 2251 (phone storage).
category_codeNoCategory code from dk_suggest or dk_categories, e.g. 'mobile-phone'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.4.0
    • removedInput schema / properties / attribute_id / title
      Removed value: -"Attribute Id"
    • removedInput schema / properties / brand_code / title
      Removed value: -"Brand Code"
    • removedInput schema / properties / category_code / title
      Removed value: -"Category Code"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"dk_filtersArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "dk_filtersDictOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.2.1

TDQS

A4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description only needs to add operational detail — and it does. It discloses the response shapes ({value title: id}, {title: id}, {code: id}, {code: title}) and the non-obvious truncation behavior for large attribute sets that forces a second call. Since there is no output schema, this disclosure is doing real work.

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?

The purpose statement is front-loaded in the first sentence, and the remaining lines are dense but each carries a distinct fact (return shapes, recursion rule, downstream consumption). The telegraphic brace/semicolon shorthand is efficient but costs some readability, keeping it from a 5.

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 carries the return-value burden and does so by describing each filter's shape. It covers both operating modes, the two-call workaround for large attribute sets, and how the ids feed into sibling tools. Minor gaps remain (e.g. seller_type semantics, price-range format beyond Toman), so not a 5.

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 description coverage is 100%, so the baseline is 3, but the description adds mode-dependent meaning the schema does not state cleanly: brands use {code: id} in category mode, categories use {code: title} in query mode. That clarifies which parameters are applicable in which operating mode, going beyond the per-field schema text.

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 — 'List the filters of a category or a search' — and enumerates the filter kinds returned (attributes, colors, sellers, price range, brands). It also names the consumer tools (dk_category_products, dk_search), which separates it from siblings like dk_categories or dk_suggest. It stops short of explicitly contrasting itself with those discovery siblings.

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?

Gives concrete when-to-use direction: pass the returned ids to dk_category_products or dk_search, and it names the exact parameter names to use. It also handles the edge case explicitly — an attribute with over 15 values returns only value_count, so call again with attribute_id. No explicit when-not-to-use or exclusions, so not a 5.

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