Skip to main content
Glama
MeltValue MCP Server

MeltValue MCP Server

by darthanalyst

Live metal spot prices

get_spot_prices
Read-onlyIdempotent

Fetch current spot prices for gold, silver, platinum, and palladium in USD per troy ounce and gram, with daily change, from MeltValue.com.

Instructions

Current spot prices for gold, silver, platinum and palladium in US dollars, per troy ounce and per gram, with the change for the day. Data from MeltValue.com.

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": "get_spot_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish this as a read-only, idempotent, open-world, non-destructive query, so the safety profile is covered. The description adds useful context by naming the data source (MeltValue.com) and the daily-change field, but says nothing about refresh cadence, caching, or whether prices can be stale or unavailable.

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 covering scope, units, currency, field included, and source, with no filler. Nothing could be cut without losing information.

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

Completeness5/5

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

With no input parameters, no output schema, and annotations covering the safety and idempotency profile, the remaining gaps an agent faces are scope and value format. The description supplies metal list, currency, dual unit basis, and the included daily change, which is sufficient to call it and interpret the result.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning to convey; the baseline applies. The description does the right thing by spending its words on scope (metals, currency, per-ounce and per-gram basis) instead of inventing inputs.

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?

Names a specific verb ('Current spot prices') and a precise resource (gold, silver, platinum, palladium), plus units and currency. An agent can tell this is a four-metal spot lookup rather than a coin-level or calculation tool, though it never explicitly contrasts itself with get_metal_price.

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 word 'Current' signals a live-quote lookup for pricing, and the four-metal scope hints it is a broad snapshot. There is no statement of when to prefer get_metal_price or calculate_melt_value, and no prerequisites or exclusions.

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