Skip to main content
Glama
digikala-mcp

digikala-mcp

by sepehr071

Digikala Plus plans

dk_plus_plans
Read-onlyIdempotent

Lists Digikala Plus plans with monthly free shipment and fresh supermarket benefits, including prices in Toman.

Instructions

List Digikala Plus plans (monthly free shipments; fresh = supermarket) with price in Toman and benefits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dk_plus_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • removedInput schema / title
      Removed value: -"dk_plus_plansArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dk_plus_plansDictOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful detail that prices come back in Toman and that benefits are included, and it decodes the 'fresh' plan as the supermarket one — modest but real context. It does not say whether the list is static or account-dependent, which matters slightly given openWorldHint=true.

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?

One front-loaded sentence with no filler; the resource comes first and the return contents follow. The parenthetical 'fresh = supermarket' is compact but slightly cryptic out of context, which is the only thing 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?

For a zero-parameter read-only list tool with no output schema, the description covers what is returned (plans, Toman prices, benefits) and clarifies a domain term. There is no output schema, so a little more detail on the shape of a plan entry would help, but nothing essential to invoking it is absent.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to document. Baseline 4 applies; no parameter meaning is missing.

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?

The description gives a specific verb and resource ('List Digikala Plus plans') plus a preview of the payload (price in Toman and benefits), so an agent knows exactly what it returns. It does not explicitly contrast with any sibling, but no sibling in the list deals with subscription plans, so the resource itself disambiguates.

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 only implied: an agent can infer this is the tool to call when a user asks about Plus subscription tiers or pricing. There is no explicit when-to-use framing, no prerequisites, and no statement of what it is not for (e.g. that it is not a product search).

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