Skip to main content
Glama

StackerScan

Spot metal prices

get_spot_prices
Read-only

Current and previous-session spot prices for gold, silver, platinum, palladium, copper and nickel, in any supported currency and per troy ounce or gram.

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
baseNoA currency code from the live catalog at /api/currencies (ISO 4217 fiat plus BTC and the metal codes). Defaults to USD.
unitNoPrice per troy ounce or per gram. Defaults to troy_oz.
metalsNoMetal symbols to include (xau gold, xag silver, xpt platinum, xpd palladium, xcu copper, ni nickel). Omit for all six; Goldback is not a spot metal.

Output Schema

NameRequiredDescriptionDefault
asOfYesUTC source update instant.
baseYesResolved uppercase currency code.
dateYesMarket or session date.
unitYesShared price denominator for every returned metal.
metalsYesRequested spot symbols only; Goldback is not a spot metal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedOutput schema / properties / metals / properties / ni / title
      Added value: +"Ohlc"
    • addedOutput schema / properties / metals / properties / xag / title
      Added value: +"Ohlc"
    • addedOutput schema / properties / metals / properties / xau / title
      Added value: +"Ohlc"
    • addedOutput schema / properties / metals / properties / xcu / title
      Added value: +"Ohlc"
    • addedOutput schema / properties / metals / properties / xpd / title
      Added value: +"Ohlc"
    • addedOutput schema / properties / metals / properties / xpt / title
      Added value: +"Ohlc"
    • addedOutput schema / properties / metals / title
      Added value: +"SpotMetals"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine scope context beyond that: which session(s) are reported and that currency/unit are open-ended ('any supported currency'). It says nothing about freshness, refresh cadence, or what happens when an unsupported currency is requested — the openWorldHint risk an agent most needs warned about.

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 that spends its words on scope rather than repeating the name. Every clause (metals, currency, unit) maps to a parameter decision, and nothing is extraneous.

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 three optional parameters at full schema coverage, an output schema, and annotations covering the safety profile, the description is nearly complete for this complexity. The remaining gap is sibling differentiation — an agent still lacks an in-description reason to pick this over get_price_history.

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 description coverage is 100%, and the schema already documents defaults (USD, troy_oz), the six metal enums, and the /api/currencies catalog constraint for base. The description restates the currency and unit dimensions in prose without adding syntax or format meaning, so the baseline 3 applies.

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 the resource (spot prices) and enumerates the exact coverage: gold, silver, platinum, palladium, copper and nickel, in any supported currency, per troy ounce or gram. That is far more specific than the title. It stops short of naming the sibling it is not — notably get_price_history — so an agent must infer that this is the current/snapshot endpoint rather than the historical one.

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?

The phrase 'current and previous-session' implicitly frames this as the snapshot tool and hints at a contrast with get_price_history, but no alternative is named and no condition is stated for choosing between them. There is also no guidance on when to omit the metals array versus enumerating it, which is the main selection decision an agent faces.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources