Skip to main content
Glama
digikala-mcp

digikala-mcp

by sepehr071

Installment plans

dk_installments
Read-onlyIdempotent

Retrieve Digipay credit-line installment offers for a product in Toman, showing fixed credit lines repaid in months rather than product-priced monthly payments.

Instructions

Get the Digipay credit-line offers for a product, in Toman.

A plan is a fixed credit line repaid in months installments, not sized to the product price: never present it as "this product for X a month".

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_id": "<product_id>"
    },
    "name": "dk_installments"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • removedInput schema / properties / product_id / description
      Removed value: -"Digikala product id, the number in 'dkp-<id>' (from dk_search etc.), e.g. 20109389."
  2. Changed3 schema fields changedv0.4.0
    • removedInput schema / properties / product_id / title
      Removed value: -"Product Id"
    • removedInput schema / title
      Removed value: -"dk_installmentsArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dk_installmentsDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world behavior, so the bar is lower. The description still adds real semantic context: results are fixed credit lines repaid over months, not payment amounts derived from the product price, plus the currency. That tells the agent how to interpret and present the output, which annotations cannot convey.

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: purpose first, a usage caveat second. No filler, and the caution about how to present plans is well placed. The caveat phrasing is slightly prescriptive but earns its space by preventing a misrepresentation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A single-parameter read tool with no output schema, so the description should say enough about what a returned plan contains (e.g. months, amount, provider) or what happens when no offers exist. It covers intent and the conceptual meaning of a plan but leaves the response shape to discovery.

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 0% and product_id has no per-field description, so the description has to carry weight; it only says the offers are 'for a product', which maps the parameter but adds no constraint, format or validity details beyond the schema's integer bounds. Adequate but not compensating for the coverage gap.

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: fetch Digipay credit-line offers for a product, with the unit (Toman). It distinguishes itself conceptually from a plans/pricing tool by explaining that plans are credit lines rather than price slices, though it never names a sibling tool to contrast with.

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?

Usage is implied by the required product_id and the phrase 'for a product', so an agent can infer it is per-product financing lookup. There is no explicit statement of when to prefer this over dk_plus_plans or dk_find_cheapest, and no exclusion guidance for products without offers.

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