Skip to main content
Glama
milligold-mcp

milligold-mcp

by sepehr071

Milli.gold fees

mg_fees
Read-onlyIdempotent

Retrieves current Milli.gold fees for buying, selling, transferring, delivering gold and wallet withdrawals, showing percent, minimum, and maximum caps for individual or company accounts.

Instructions

Get Milli.gold's current fees for buying, selling, transferring and delivering gold and for wallet withdrawals.

Each fee is percent of the amount, at least min and at most max ('none' = no cap); mg = milligrams of gold. To price a concrete trade use mg_trade_quote.

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

Input Schema

NameRequiredDescriptionDefault
customerNoAccount type.individual

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / customer / description
      Previous value: -"individual = personal account, company = business account."New value: +"Account type."
  2. Addedv0.2.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so safety needs no restating. The description adds context the annotations cannot: the fee model itself (each fee is a percent of the amount with min/max bounds, 'none' meaning uncapped, mg = milligrams). It does not mention rate limits, caching freshness, or whether fees vary over time, but nothing contradicts the annotations.

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 paragraphs, front-loaded with the purpose and followed by the data-shape convention needed to read the result. Every clause carries information: the fee domains, the min/max/percent model, and the 'none' and 'mg' conventions all matter and none is repeated.

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?

There is no output schema, and the description compensates by explaining the shape of each fee entry (percent, min, max, 'none', mg units), which is exactly what an agent needs to interpret the response. The remaining gap is the unexplained effect of the `customer` parameter on the returned fees.

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 coverage is 100% and the single enum parameter `customer` is fully documented in the schema, so the baseline of 3 applies. However, the description never explains the material semantic question of whether individual vs. company accounts receive different fee schedules, which is the only reason that parameter exists.

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 Milli.gold's current fees") and enumerates the scopes covered: buying, selling, transferring, delivering, and wallet withdrawals. It also names the sibling to use for the adjacent job (mg_trade_quote), so an agent can distinguish it from mg_get_price and mg_trade_quote 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 Guidelines4/5

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

The routing rule is explicit: this tool is for fee schedules, and "to price a concrete trade use mg_trade_quote." That is a clear alternative-with-condition. There is no stated exclusion for the price/history siblings (mg_get_price, mg_price_history), which would have made it a 5.

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