Skip to main content
Glama
digikala-mcp

digikala-mcp

by sepehr071

Compare products

dk_compare
Read-onlyIdempotent

Compare 2-4 products side by side to see price and rating differences plus the spec rows that actually differ. Use it to pick the better product.

Instructions

Compare 2-4 products side by side: price and rating, then the spec rows where they differ.

A specs row's values follow products order (null = no such spec); identical rows fold into same_specs.

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_ids": "<product_ids>"
    },
    "name": "dk_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idsYesSame kind, e.g. [20109389, 20110013].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / product_ids / description
      Previous value: -"2-4 product ids of the same kind, e.g. [20109389, 20110013]."New value: +"Same kind, e.g. [20109389, 20110013]."
  2. Changed3 schema fields changedv0.4.0
    • removedInput schema / properties / product_ids / title
      Removed value: -"Product Ids"
    • removedInput schema / title
      Removed value: -"dk_compareArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dk_compareDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety burden is lifted. The description still earns credit by disclosing the return shape: a specs row's values align to products order, null means the spec is absent, and identical rows are folded into same_specs — non-obvious output semantics with no output schema to carry them.

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 sentences, both load-bearing: the first states what is returned, the second states how to read the alignment-sensitive parts. Front-loaded with the core purpose and free of filler.

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 one required parameter, no output schema, and full annotation coverage, the definition is nearly sufficient — the response shape (price, rating, differing specs, same_specs) is spelled out. Minor gaps remain: ordering of the top-level products array and any error behavior for invalid or mismatched product pairs are unstated.

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 100% and the schema already states minItems 2 / maxItems 4 and the integer-array type, so the description's "2-4 products" is largely redundant. The one piece of added meaning — that values follow products order — describes output alignment rather than the input parameter itself, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Compare 2-4 products side by side: price and rating, then the spec rows where they differ" names a specific verb (compare), resource (products), and even the comparison axes and diff-filtering behavior. This clearly separates it from siblings like dk_product (single lookup) and dk_similar (recommendations), so an agent can pick it without opening a schema.

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

Usage Guidelines3/5

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

The description implies the use case (side-by-side comparison of 2-4 items) but never states when to prefer it over dk_similar, dk_product, or dk_shortlist, nor any preconditions such as products needing to be the same kind. Usage is inferable from the name and the 2-4 bound, not explicitly guided.

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