Skip to main content
Glama
MeltValue MCP Server

MeltValue MCP Server

by darthanalyst

Price of one metal

get_metal_price
Read-onlyIdempotent

Retrieves the current spot price of gold, silver, platinum, or palladium in USD per troy ounce, gram, and kilogram, including daily change.

Instructions

Current spot price of one precious metal in US dollars per troy ounce, gram and kilogram, with the change for the day. Data from 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>"
    },
    "name": "get_metal_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
metalYesWhich metal to price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/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, openWorld, non-destructive), and the description adds genuine value beyond them: the currency, the three weight bases returned, the inclusion of daily change, and the upstream source (MeltValue.com). It stops short of noting data freshness or caching behavior.

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?

A single front-loaded sentence with no filler; the unit bases and the daily-change note are packed into the same clause set without redundancy. Every clause carries information an agent would otherwise have to guess.

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 usefully sketches the return shape (three unit bases plus day change) so the agent knows what to expect. For a one-parameter read-only lookup this is close to complete, missing only freshness or failure behavior.

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% with a fully enumerated metal field, so the schema already carries the parameter meaning. The description contributes only the framing that the value is a precious metal and how the result is denominated, which is baseline-level support.

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 and resource ('Current spot price of one precious metal') and pins down units (USD per troy ounce, gram, kilogram) plus the daily change. The word 'one' implicitly separates it from the plural sibling get_spot_prices, though no sibling is named explicitly.

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: pricing 'one' metal suggests the single-metal case versus a bulk-prices sibling, but the description never states when to prefer it over get_spot_prices or calculate_melt_value, nor any exclusions. Adequate but leaves routing to inference.

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