Skip to main content
Glama
iran-gold-mcp

iran-gold-mcp

by sepehr071

Milli.gold price history

gold_milli_history
Read-onlyIdempotent

Retrieve Milli.gold 18k gold price history for daily, weekly, or monthly periods, including high, low, and change values. Use it to track price movements over time.

Instructions

Get the Milli.gold 18k gold price series for a day, week or month, with high, low and change.

Rial per milligram (x100 = Toman per gram), Tehran time. For today's price on every platform use gold_prices.

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": "gold_milli_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoWindow: DAILY = last ~24 h (15-min points), WEEKLY = last week, MONTHLY = last ~month.DAILY
pointsNoMax points to return, evenly spaced (2-50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely non-structured context: the unit convention ('Rial per milligram, x100 = Toman per gram') and the Tehran timezone, both of which materially affect interpretation of results. It stops short of stating any rate-limit or freshness guarantees beyond what the period enum implies.

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 sentences, both earning their place: the first defines the capability and return shape, the second carries the disambiguation and unit/timezone caveats. The differentiator is front-loaded in the opening clause.

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 2-parameter read tool with full schema coverage and rich annotations, the definition covers scope, units, timezone, and the sibling alternative. The only minor gap is that the return shape is summarized as 'high, low and change' without mentioning the underlying series points that the points parameter controls, and gold_milli_stats is never distinguished.

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?

Schema description coverage is 100%, so both the period enum and the points range (2-50, evenly spaced) are already fully documented. The description's 'day, week or month' phrasing merely restates the enum labels and adds no syntax or unit detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Get the Milli.gold 18k gold price series'), the supported windows, and the returned aggregates (high, low, change). It also names the sibling it is not ('For today's price on every platform use gold_prices'), so an agent can route without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gives the alternative and the selection condition: this tool for historical series, gold_prices for today's cross-platform price. That is a concrete when-to-use/when-not pair rather than inferred usage.

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