Skip to main content
Glama
milligold-mcp

milligold-mcp

by sepehr071

Milli.gold trade cost quote

mg_trade_quote
Read-onlyIdempotent

Estimate the Toman cost of a gold buy or the payout of a gold sale at the live price, with fees included. Enter grams for either side or a Toman budget for a buy quote.

Instructions

Estimate what a gold trade on Milli.gold costs or pays out right now, fee included, at the live price.

Give grams (buy or sale) or toman (buy budget). Returns pay_toman for a buy, receive_toman for a sale. Estimate only: new-user fee waivers and withdrawal fees are not applied. Fee table: mg_fees.

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": {
      "side": "<side>"
    },
    "name": "mg_trade_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYesYour side of the trade.
gramsNo18k gold in grams, e.g. 0.5.
tomanNoBuy only: budget in Toman, fee included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.0
    • changedInput schema / properties / grams / description
      Previous value: -"Amount of 18k gold in grams (e.g. 0.5)."New value: +"18k gold in grams, e.g. 0.5."
    • changedInput schema / properties / side / description
      Previous value: -"buy = you buy gold, sell = you sell gold."New value: +"Your side of the trade."
    • changedInput schema / properties / toman / description
      Previous value: -"Buy only: total budget in Toman, fee included (e.g. 5000000)."New value: +"Buy only: budget in Toman, fee included."
  2. Addedv0.2.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's value is in the caveats: the quote is a live snapshot, fee is included, and new-user fee waivers and withdrawal fees are NOT applied. That is a genuinely useful limitation disclosure an agent would otherwise misreport. It stops short of saying how live/fresh the price is or what happens at the extremes of the range.

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 front-loaded lines: what it computes, how to parameterize it, and the disclosure caveat. Every sentence earns its place and nothing is padded.

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 output schema, the description correctly names the return fields (`pay_toman`, `receive_toman`) and flags the estimate's exclusions, which is enough to call it responsibly. Minor gaps remain: no guidance on supplying both `grams` and `toman`, or on the practical bounds (0 < grams ≤ 100000) enforced by the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds real meaning: it clarifies the either/or choice between `grams` and `toman` (which the schema does not enforce via oneOf) and that `toman` is a buy-only, fee-inclusive budget. It also maps the parameters to outcomes (`pay_toman` for buy, `receive_toman` for sale), which the schema alone cannot convey.

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: estimating the toman cost or payout of a gold trade on Milli.gold, fee included, at the live price. It is clearly a quote calculator rather than a price feed (mg_get_price) or a fee table (mg_fees), and an agent can distinguish it without opening the schema.

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?

Gives concrete input guidance ('Give `grams` (buy or sale) or `toman` (buy budget)') and routes the agent to mg_fees for the underlying fee table. It also sets the expectation 'Estimate only', implying this precedes an actual trade, but it never explicitly states when not to use it or names mg_get_price as the alternative for pure pricing.

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