Skip to main content
Glama
digikala-mcp

digikala-mcp

by sepehr071

Gold and coin prices

dk_gold_prices
Read-onlyIdempotent

Retrieve live 18k gold price per gram and gold coin prices in Toman, with ~3-month change, low, and high; a null coin price means not for sale.

Instructions

Get the live 18k gold price per gram and gold coin prices, in Toman.

Period change, low and high cover ~3 months. A coin with price null is not for sale.

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

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_gold_pricesArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "dk_gold_pricesDictOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description goes beyond them by disclosing freshness ("live"), the ~3-month window behind period change/low/high, and the meaning of a null coin price (not for sale), which is genuinely useful edge-case context.

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?

Two short sentences with zero filler; the primary capability is front-loaded and the caveats (time window, null prices) follow. Every sentence carries information the agent could not get elsewhere.

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

Completeness5/5

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

For a parameterless read tool with no output schema, the description covers what is returned (gram price, coin prices), the unit, the time horizon of derived fields, and the null case. Nothing needed to interpret the response is missing.

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, so the baseline is 4; there is nothing for the description to disambiguate. It still adds value by pinning down the currency and the karat (18k), which the empty schema cannot express.

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 uses a specific verb and resource ("Get the live 18k gold price per gram and gold coin prices") and even names the unit (Toman), so an agent knows exactly what data comes back. It does not explicitly contrast itself with siblings, but no sibling covers gold/coin pricing, so the risk of misselection is low.

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 data named (live gold and coin prices) rather than stated as explicit when-to-use/when-not guidance, and no alternative tool is referenced. Adequate but leaves the agent to infer that this is the only pricing source.

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