Skip to main content
Glama

Metals Api Get Latest

metals_api_get_latest
Read-onlyIdempotent

Get the latest precious and base metal spot prices (gold, silver, platinum, palladium, copper, etc.). Prices are per troy ounce. Optionally specify base currency and metal symbols.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "_apiKey": "your-metals-api-key"
    },
    "name": "metals_api_get_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoBase currency (default "USD"). E.g., "EUR", "GBP"
_apiKeyYesMetals-API key
symbolsNoComma-separated metal symbols to filter (e.g., "XAU,XAG,XPT"). XAU=gold, XAG=silver, XPT=platinum, XPD=palladium, XCU=copper

Output Schema

NameRequiredDescriptionDefault
baseYesBase currency code (e.g., USD, EUR)
dateYesDate of the latest prices in YYYY-MM-DD format
ratesYesMetal spot prices per troy ounce, keyed by symbol (e.g., XAU, XAG)
timestampYesUnix timestamp of when prices were captured

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety and reproducibility profile is fully covered. The description adds genuine context beyond that — the unit of measure ('per troy ounce') and the fact that results can be rebased to another currency — but says nothing about freshness/latency of the spot quote, rate limits, or the required API key handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and the unit-of-measure qualifier before the optional-parameter note. The third sentence is largely redundant with the schema and could be dropped without loss, which keeps it just below top marks.

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 an output schema present the description needn't explain return values, and annotations cover the safety profile, so the remaining burden is small. It covers what data is returned and its unit, but leaves the required _apiKey/auth expectation implicit — an agent must read the schema to learn the call will fail without credentials.

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%, with base, symbols, and _apiKey each documented including the USD default and the XAU/XAG/XPT/XPD/XCU symbol legend. The description restates the optionality of base and symbols without adding format or constraint detail beyond the schema, 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 opens with a specific verb and resource: 'Get the latest precious and base metal spot prices,' and enumerates the metals covered (gold, silver, platinum, palladium, copper). The word 'latest' implicitly separates it from the sibling metals_api_get_historical, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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 when to prefer the historical sibling or any other tool. The only conditional language ('Optionally specify base currency and metal symbols') is parameter-level, not task-level, so an agent gets no routing advice.

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.