Skip to main content
Glama
sepehr071

digikala-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Gold and coin prices

dk_gold_prices
Read-onlyIdempotent

Fetch live 18k gold price per gram and gold coin prices in Toman, including daily change, 3-month range, and coin sale availability.

Instructions

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

gold18_day_change_pct is vs the previous daily point; period change, low and high cover the ~3-month chart. Coins' change_pct is as Digikala shows it. Coins with price null are not for sale.

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.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior. The description adds genuinely useful field semantics beyond that: what gold18_day_change_pct compares against, that period change/low/high span a ~3-month chart, and that a null coin price means 'not for sale.' This is real context the annotations do not carry.

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?

Front-loaded purpose sentence followed by a compact field-glossary paragraph; every sentence earns its place. The second block is slightly terse ('period change, low and high') but not wasteful.

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?

With no parameters and no output schema, the description must convey what comes back, and it partially does by defining several return fields. It does not enumerate the full response shape (e.g., the coin list structure), leaving a small gap for a tool whose return values carry the whole contract.

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?

With zero parameters, the baseline is 4. The description instead spends its text on return-field semantics, which is the right allocation for a no-argument tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource: 'Get the live 18k gold price per gram and gold coin prices, in Toman.' No sibling tool in the list covers market/commodity pricing, so it is trivially distinguished from the product-search siblings.

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?

The description gives clear context (live gold/coin prices) but no explicit when-to-use/when-not guidance. Because it takes no parameters and no sibling overlaps this resource, the usage is unambiguous without routing instructions.

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