Skip to main content
Glama
digikala-mcp

digikala-mcp

by sepehr071

Find location

dk_location
Read-onlyIdempotent

Converts a Persian address or landmark into coordinates, or coordinates into an address, returning Digikala city_id and state_id to determine delivery location.

Instructions

Turn an address into coordinates, or coordinates into an address with Digikala's city_id and state_id.

Prices are the same everywhere; location only affects delivery.

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_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoWith long: describe a point instead.
cityNoPersian city, e.g. 'تهران'; needed for most addresses.
longNo
addressNoPersian address or landmark, e.g. 'میدان ونک'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changedv0.6.0
    • removedInput schema / properties / address / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 200,
      -    "minLength": 2,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / address / description
      Previous value: -"Address or landmark in Persian, e.g. 'میدان ونک'. Latin text matches poorly."New value: +"Persian address or landmark, e.g. 'میدان ونک'."
    • addedInput schema / properties / address / maxLength
      Added value: +200
    • addedInput schema / properties / address / minLength
      Added value: +2
    • addedInput schema / properties / address / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / city / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 50,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / city / description
      Previous value: -"Persian city name; without it most addresses find nothing, e.g. 'تهران' or 'مشهد'."New value: +"Persian city, e.g. 'تهران'; needed for most addresses."
    • addedInput schema / properties / city / maxLength
      Added value: +50
    • addedInput schema / properties / city / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / lat / anyOf
      Removed value: -[
      -  {
      -    "maximum": 40,
      -    "minimum": 24,
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude, to describe a point instead (Iran: ~25 to ~40)."New value: +"With long: describe a point instead."
    • addedInput schema / properties / lat / maximum
      Added value: +40
    • addedInput schema / properties / lat / minimum
      Added value: +24
    • addedInput schema / properties / lat / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedInput schema / properties / long / anyOf
      Removed value: -[
      -  {
      -    "maximum": 64,
      -    "minimum": 44,
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / long / description
      Removed value: -"Longitude, with lat."
    • addedInput schema / properties / long / maximum
      Added value: +64
    • addedInput schema / properties / long / minimum
      Added value: +44
    • addedInput schema / properties / long / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. Changed6 schema fields changedv0.4.0
    • removedInput schema / properties / address / title
      Removed value: -"Address"
    • removedInput schema / properties / city / title
      Removed value: -"City"
    • removedInput schema / properties / lat / title
      Removed value: -"Lat"
    • removedInput schema / properties / long / title
      Removed value: -"Long"
    • removedInput schema / title
      Removed value: -"dk_locationArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dk_locationDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/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 profile is covered. The description adds domain behavior — that location affects only delivery and not price — which is genuinely useful. It says nothing about coverage limits (Iran-only bbox), ambiguous-address handling, or what happens on failure, so a 3 fits.

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, front-loaded with the core operation. The second sentence is a slight aside but short enough to earn its place by deterring unnecessary calls.

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?

The tool is simple and the description names the returned concepts, which partly compensates for the missing output schema. However, with four optional parameters and none required, the definition never states which combination is valid or what happens when no argument is supplied.

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 coverage is 75%, but the description does real work by framing the two parameter modes (address/city vs lat/long) and implying they are alternatives. That pairing is not stated in the schema, where all four params are nullable with zero required.

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 concrete verb and resource pair in both directions (address→coordinates, coordinates→address) and names the Domain-specific outputs (city_id, state_id). None of the siblings deal with geocoding, so differentiation is implicit rather than stated.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The line 'Prices are the same everywhere; location only affects delivery' hints at why an agent might need this at all, but an agent still has to infer the trigger condition.

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