Metals Api

Get Latest

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

Input Schema

Name	Required	Description
`base`	No	Base currency (default "USD"). E.g., "EUR", "GBP"
`_apiKey`	Yes	Metals-API key
`symbols`	No	Comma-separated metal symbols to filter (e.g., "XAU,XAG,XPT"). XAU=gold, XAG=silver, XPT=platinum, XPD=palladium, XCU=copper

Output Schema

Name	Required	Description
`base`	Yes	Base currency code (e.g., USD, EUR)
`date`	Yes	Date of the latest prices in YYYY-MM-DD format
`rates`	Yes	Metal spot prices per troy ounce, keyed by symbol (e.g., XAU, XAG)
`timestamp`	Yes	Unix timestamp of when prices were captured

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 26, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety. The description adds that prices are per troy ounce and that base/symbols are optional. This is useful but does not disclose potential rate limits, response format details, or any non-obvious behavior beyond the annotations.

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?

The description is two sentences, front-loaded with the primary purpose, and includes only the essential extra details (per troy ounce, optional parameters). No filler or redundancy; every word adds value.

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?

This is a simple data retrieval tool with rich annotations, a fully documented input schema, and an output schema. The description sufficiently covers the core behavior, units, and optional parameters. No significant gaps remain, and the description is complete for what the tool does.

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%, so the schema already fully documents 'base', '_apiKey', and 'symbols'. The description's mention of optional base currency and symbols is redundant with the schema. It adds no additional semantics or syntax details beyond what the schema already provides, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves 'latest precious and base metal spot prices' with specific metals and a per-ounce unit. The verb 'Get' combined with the resource and scope provides a clear, specific purpose. It also implicitly differentiates from siblings like get_historical by emphasizing 'latest'.

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 description implies usage when current spot prices are needed, and notes optional parameters for base currency and symbols. However, it does not explicitly mention when not to use it or name alternative tools (e.g., get_historical for historical data). Usage is clear but not explicitly differentiated from siblings.

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

All Metals Api tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.