Skip to main content
Glama
digikala-mcp

digikala-mcp

by sepehr071

Search suggestions

dk_suggest
Read-onlyIdempotent

Autocompletes vague or misspelled queries into suggested keywords and categories to help refine product searches and improve discovery.

Instructions

Autocomplete a vague or misspelled query into keywords and categories.

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": {
      "query": "<query>"
    },
    "name": "dk_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPartial text, e.g. 'هدفون'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / query / description
      Previous value: -"Partial text, e.g. 'samsung' or 'هدفون'."New value: +"Partial text, e.g. 'هدفون'."
  2. Changed3 schema fields changedv0.4.0
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"dk_suggestArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dk_suggestDictOutput",
      -  "type": "object"
      -}New value: +null
  3. 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, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds that the output is keywords and categories rather than results, which is useful context, but it says nothing about how many suggestions are returned or whether the caller should re-issue a search with 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?

A single sentence with no wasted words, and the qualifier (vague or misspelled) is front-loaded before the output description.

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 suggestion tool with full annotation coverage and no output schema, the description conveys input conditions and the rough shape of the return value. Only the intended follow-up workflow (use the returned keywords with a search tool) is left implicit.

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?

With one parameter and 100% schema coverage, the schema already documents the input as partial text with an example. The description reinforces that the query may be vague or misspelled, but adds no length, language, or formatting constraints beyond the schema.

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 (autocomplete) and the transformation applied to the input (vague or misspelled query → keywords and categories). This makes the tool's role distinguishable from a plain search like dk_search, though it never names the sibling it complements.

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?

"Vague or misspelled query" implies when the tool is appropriate, but there is no explicit when-not guidance or pointer to alternatives such as dk_search for well-formed queries. The agent must infer the routing rule.

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