Skip to main content
Glama

Metals Api Get Historical

metals_api_get_historical
Read-onlyIdempotent

Get metal prices for a specific historical date. Returns spot prices per troy ounce for that day. Useful for tracking price changes or computing returns.

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": {
      "date": "2024-01-15",
      "_apiKey": "your-metals-api-key"
    },
    "name": "metals_api_get_historical"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoBase currency (default "USD")
dateYesDate in YYYY-MM-DD format (e.g., "2024-01-15")
_apiKeyYesMetals-API key
symbolsNoComma-separated metal symbols (e.g., "XAU,XAG")

Output Schema

NameRequiredDescriptionDefault
baseYesBase currency code (e.g., USD, EUR)
dateYesHistorical date 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

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's main added value is stating the return unit and per-day granularity. It does not disclose anything about historical date-range limits, behavior when a date has no data, or how the _apiKey requirement manifests at call time — gaps that matter for an open-world external API.

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 followed by return format and a use case. No redundant restatement of the title, though the third sentence is the weakest and could be trimmed.

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 simple single-date read tool with a fully documented schema and an output schema covering return values, the description is largely sufficient — purpose, unit, and granularity are all stated. Minor incompleteness remains around currency/date-range behavior, but nothing critical is missing to invoke it correctly.

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 all four parameters (date, base, symbols, _apiKey) are already documented with formats and examples, setting the baseline at 3. The description adds no meaning beyond the schema — it doesn't explain what 'base' changes about the returned prices or how 'symbols' filtering interacts with the per-troy-ounce figures.

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?

States a specific verb and resource ('Get metal prices') scoped to 'a specific historical date', and the second sentence clarifies the return unit (spot prices per troy ounce). The word 'historical' implicitly distinguishes it from metals_api_get_latest, though the sibling is never named explicitly.

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?

'Useful for tracking price changes or computing returns' gives downstream use cases but not invocation guidance — it never says when to prefer this over metals_api_get_latest or what date ranges are valid. Usage is only implied by the word 'historical'.

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.