Skip to main content
Glama
milligold-mcp

milligold-mcp

by sepehr071

Milli.gold live gold price

mg_get_price
Read-onlyIdempotent

Fetch the current Milli.gold 18k melted-gold price in Rial per milligram and gram, excluding tax and making charges.

Instructions

Get the current Milli.gold price of 18k melted gold, in Rial per milligram and per gram.

Platform's own price, no tax or making charge. For trends use mg_price_history.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/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 real semantic value by clarifying that this is the platform's own price with no tax or making charge, which tells the agent what the number means. It says nothing about update cadence, caching, or whether the price can be stale, which matters for a 'current price' tool.

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?

Three short sentences, front-loaded with what is returned and in which units, followed by the pricing caveat and the sibling redirect. No filler or redundancy.

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 trivial no-parameter read with no output schema, the description covers what is returned (price per mg and per gram), the currency, and the pricing basis. The only meaningful gap is that it does not describe the shape of the returned payload or how often the value refreshes.

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 no parameters, so there is nothing schema-side to explain; the baseline for a zero-parameter tool applies. The description does not waste space restating the empty input.

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 ('Get'), a precise resource ('current Milli.gold price of 18k melted gold'), and even the units (Rial per milligram and per gram). It is unmistakable against siblings such as mg_price_history or mg_trade_quote.

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?

Explicitly routes trend-seeking callers to mg_price_history, which is the main ambiguity for a price tool. It does not address other adjacent cases (e.g. quoting a trade, which mg_trade_quote presumably covers) or distinguish freshness expectations.

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