Skip to main content
Glama
MeltValue MCP Server

MeltValue MCP Server

by darthanalyst

US coin melt value

get_coin_melt_value
Read-onlyIdempotent

Calculate the live melt value in US dollars for common US gold and silver coins based on precious metal content and quantity, using current spot prices.

Instructions

Melt value in US dollars of common US gold and silver coins at the live spot price, based on each coin's precious metal content. Collector value can be higher. 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": {
      "coin": "<coin>"
    },
    "name": "get_coin_melt_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesWhich coin.
quantityNoHow many coins. Defaults to 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/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, openWorld), so the bar is lowered, yet the description still adds real context: the figure is metal-content only, at the live spot price (therefore time-varying), explicitly excluding numismatic premium, with MeltValue.com as the source. It does not discuss output shape or precision, which keeps it below a 5.

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, the core definition first, the caveat second, the attribution last. Nothing is redundant or padded, and the key scope limit is front-loaded.

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 carries the burden of explaining the return value and does so adequately ('melt value in US dollars'), plus a clear caveat about what is excluded. The one gap is that it never clarifies how the quantity parameter is reflected in the result, which an agent would want to know for a tool with no structured output contract.

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%, so both parameters are already documented in the input schema and the baseline of 3 applies. The description adds nothing about the coin enumeration or about how quantity affects the returned value (whether the result is per-coin or total), so no credit above baseline.

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 names a specific verb+resource: the melt value in USD of common US gold and silver coins, computed from metal content at the live spot price. The coin scope does implicitly separate it from the generic calculate_melt_value / get_spot_prices siblings, but it never states that distinction explicitly, so an agent must infer the routing.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of any alternative tool, even though calculate_melt_value sits in the sibling list and looks adjacent. The only adjacent statement, 'Collector value can be higher,' is a caveat about the returned number, not usage guidance.

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