Skip to main content
Glama
sepehr071

digikala-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Installment plans

dk_installments
Read-onlyIdempotent

Fetch Digipay credit-line installment offers for a Digikala product by product ID, showing fixed credit amount, monthly repayment, and terms in Toman. Check product ID first; approval required.

Instructions

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

A plan is a fixed credit line (credit_amount) repaid in months installments of monthly_repayment; it is not sized to the product price, so never present it as "this product for X a month". Needs Digipay approval. An unknown id gives no plans; check it with dk_product.

Input Schema

NameRequiredDescriptionDefault
product_idYesDigikala product id, the number in 'dkp-<id>' (from dk_search etc.), e.g. 20109389.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered; the description adds genuinely non-obvious behavioral facts on top: an approval requirement, empty-result behavior on unknown ids, and the warning that plans are not sized to the product price so they must not be framed as a per-month product offer.

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?

Three tight sentences with the purpose front-loaded, then the domain caveat, then the prerequisite and error behavior. Nothing is padded, though the mid-sentence backtick identifiers make it slightly denser than needed.

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 one-parameter read-only lookup with no output schema, the description supplies the missing return-shape vocabulary, the approval prerequisite, and the invalid-id behavior. The only gap is that it never contrasts with the sibling dk_plus_plans, leaving the agent to guess which plan tool fits which product type.

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 the single product_id parameter is already well documented in the schema (format, example, range), so the schema carries the load. The description adds only the currency unit (Toman) and output-field vocabulary (credit_amount, months, monthly_repayment), which are return-value semantics rather than parameter semantics.

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 (Get) and resource (Digipay credit-line offers for a product) and even names the price unit (Toman). It defines what an installment plan is, but never explicitly distinguishes itself from the nearby sibling dk_plus_plans, which an agent could plausibly confuse it with.

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 a real prerequisite ("Needs Digipay approval"), tells the agent what happens with a bad input ("An unknown id gives no plans"), and routes to a validator ("check it with dk_product"). It stops short of an explicit when-to-use-vs-alternative statement (e.g. vs dk_plus_plans), so it is clear context but not full exclusion guidance.

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