Skip to main content
Glama

Get Live Spot Prices

get_live_spot_prices
Read-only

Get live Gold (XAU), Silver (XAG), Platinum (XPT), and Palladium (XPD) spot prices in USD per troy ounce, plus the real-time Gold-to-Silver Ratio (GSR).

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_live_spot_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that — quote currency (USD), units (per troy ounce), and the inclusion of GSR — but says nothing about update cadence, market-closed behavior, or data source, which matter for a 'live' pricing tool.

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 sentence with the resource front-loaded and every clause earning its place — tickers, currencies, units, and the extra GSR output are all decision-relevant. No filler or restatement of the title.

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?

For a zero-parameter, no-output-schema tool, the description does the essential work of naming the values returned and their units and currency. It stops short of describing response shape (field names, timestamps, freshness indicators), which matters because no output schema exists to fall back on.

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?

Zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly signals the tool is parameterless by describing a fixed, fully specified output set.

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?

Specific verb ('Get') plus a precisely enumerated resource: Gold (XAU), Silver (XAG), Platinum (XPT), Palladium (XPD) spot prices and the Gold-to-Silver Ratio. The 'spot' qualifier is what separates it from siblings such as get_dealer_price_position or get_premium_index, but that distinction is only implicit rather than named.

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?

No explicit statement of when to choose this over dealer-price or premium tools; guidance is only implied by the narrow 'live spot' framing. An agent can infer that this is the spot-price source, but the description never says 'use this for X, use sibling Y for Z'.

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