Skip to main content
Glama
MeltValue MCP Server

MeltValue MCP Server

by darthanalyst

Melt value calculator

calculate_melt_value
Read-onlyIdempotent

Calculate the live USD melt value of gold, silver, platinum, or palladium items from weight and purity. Use karat or fineness to estimate intrinsic metal content and buyer offer benchmarks.

Instructions

Melt value in US dollars of an item made of gold, silver, platinum or palladium, from its weight and purity at the live spot price. Give purity as karat (gold, for example 14) or as fineness (for example 0.925 for sterling silver). Melt value is the metal content value; buyers pay a percentage of it. Calculation by MeltValue.com.

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": {
      "metal": "<metal>",
      "weight": "<weight>"
    },
    "name": "calculate_melt_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoUnit of the weight. Defaults to gram. "ounce" is the ordinary 28.35 g ounce; "troy_ounce" is 31.1 g.
karatNoGold purity in karats, 1 to 24. Use this or fineness.
metalYesMetal the item is made of.
weightYesWeight of the item.
finenessNoPurity as a decimal fraction, for example 0.925, 0.999 or 0.585. Use this or karat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already cover read-only, idempotent, non-destructive and openWorld, so the description's job is narrower. It usefully confirms that pricing is at the *live* spot price and attributes the calculation to MeltValue.com, plus warns that melt value is metal content only and buyers pay a percentage. It does not disclose spot-price freshness, caching, or failure behavior — relevant gaps for an openWorld tool.

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?

Three short sentences, front-loaded with the result being computed and the inputs it needs. The closing attribution to MeltValue.com is mild filler but does not obstruct scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the return-value burden: it states the result is a USD figure but not whether the response includes the spot price used, the purity basis, or any breakdown. For a five-parameter calculation against live market data, that is adequate but leaves the agent guessing about the response shape.

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?

With 100% schema description coverage the baseline is 3. The description reinforces the karat-vs-fineness choice and gives a concrete sterling example, but says nothing about unit or weight semantics, which the schema already handles better (troy ounce vs ordinary ounce).

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

Purpose4/5

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

The description opens with a precise verb+resource+output: computes melt value in USD for an item of gold, silver, platinum or palladium from weight and purity at the live spot price. That is enough to separate it from a coin-specific calculator or a raw price feed, but it never names the siblings (get_coin_melt_value, get_spot_prices) so the agent must infer the boundary itself.

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

Usage Guidelines3/5

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

Usage is only implied: the tool is a general item calculator, and the purity sentence ('give purity as karat ... or as fineness') tells the agent how to call it. There is no explicit when-to-use versus get_coin_melt_value for a coin, nor any note about required inputs beyond the schema's required fields.

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