FXMacroData

Commodity Indicators

commodities

Read-only

Get historical price series for supported commodity indicators using the exact slugs advertised by this schema. Requires an API key. Supported indicators: crude_oil_inventories, gold, natural_gas, natural_gas_storage, oil_brent, oil_wti, platinum, silver. Access: requires an FXMacroData API key; an anonymous call returns subscription_required with a subscribe link.

Input Schema

TableJSON Schema

Name	Required	Description
`symbol`	No	Backward-compatible alias for `indicator`, which supersedes it in new calls.
`end_date`	No	Inclusive upper bound, YYYY-MM-DD.
`indicator`	No	Commodity indicator slug. Supported: crude_oil_inventories, gold, natural_gas, natural_gas_storage, oil_brent, oil_wti, platinum, silver.
`start_date`	No	Inclusive lower bound, YYYY-MM-DD.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

changedInput schema / properties / symbol / description

Previous value: -"Backward-compatible alias for `indicator`. Prefer `indicator` in new calls."New value: +"Backward-compatible alias for `indicator`, which supersedes it in new calls."

Changed4 schema fields changedSep 7, 2026
- removedInput schema / properties / end_date / title
```
Removed value: -"End Date"
```
- removedInput schema / properties / indicator / title
```
Removed value: -"Indicator"
```
- removedInput schema / properties / start_date / title
```
Removed value: -"Start Date"
```
- removedInput schema / properties / symbol / title
```
Removed value: -"Symbol"
```

Changed3 schema fields changedJul 24, 2026

changedInput schema / properties / indicator / description

Previous value: -"Commodity indicator slug. Supported: gold, natural_gas, oil_brent, oil_wti, platinum, silver."New value: +"Commodity indicator slug. Supported: crude_oil_inventories, gold, natural_gas, natural_gas_storage, oil_brent, oil_wti, platinum, silver."

changedInput schema / properties / indicator / examples

Previous value: -[
-  "gold",
-  "natural_gas",
-  "oil_brent",
-  "oil_wti",
-  "platinum",
-  "silver"
-]New value: +[
+  "crude_oil_inventories",
+  "gold",
+  "natural_gas",
+  "natural_gas_storage",
+  "oil_brent",
+  "oil_wti"
+]

changedInput schema / properties / symbol / examples

Previous value: -[
-  "gold",
-  "natural_gas",
-  "oil_brent",
-  "oil_wti",
-  "platinum",
-  "silver"
-]New value: +[
+  "crude_oil_inventories",
+  "gold",
+  "natural_gas",
+  "natural_gas_storage",
+  "oil_brent",
+  "oil_wti"
+]

Changed5 schema fields changedJun 22, 2026

addedInput schema / properties / indicator / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / indicator / default
```
Added value: +null
```
removedInput schema / properties / indicator / type
```
Removed value: -"string"
```

addedInput schema / properties / symbol

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Backward-compatible alias for `indicator`. Prefer `indicator` in new calls.",
+  "examples": [
+    "gold",
+    "natural_gas",
+    "oil_brent",
+    "oil_wti",
+    "platinum",
+    "silver"
+  ],
+  "title": "Symbol"
+}

removedInput schema / required
```
Removed value: -[
-  "indicator"
-]
```

Changed2 schema fields changedJun 22, 2026

changedInput schema / properties / indicator / description

Previous value: -"Commodity indicator slug. Supported: gold, platinum, silver."New value: +"Commodity indicator slug. Supported: gold, natural_gas, oil_brent, oil_wti, platinum, silver."

changedInput schema / properties / indicator / examples

Previous value: -[
-  "crude_oil",
-  "natural_gas",
-  "gold",
-  "silver",
-  "copper"
-]New value: +[
+  "gold",
+  "natural_gas",
+  "oil_brent",
+  "oil_wti",
+  "platinum",
+  "silver"
+]

Changed6 schema fields changedMay 21, 2026

addedInput schema / properties / end_date / description
```
Added value: +"Inclusive upper bound, YYYY-MM-DD."
```

addedInput schema / properties / end_date / examples

Added value: +[
+  "2020-01-01",
+  "2024-06-30"
+]

addedInput schema / properties / indicator / description

Added value: +"Commodity indicator slug. Supported: gold, platinum, silver."

addedInput schema / properties / indicator / examples

Added value: +[
+  "crude_oil",
+  "natural_gas",
+  "gold",
+  "silver",
+  "copper"
+]

addedInput schema / properties / start_date / description
```
Added value: +"Inclusive lower bound, YYYY-MM-DD."
```

addedInput schema / properties / start_date / examples

Added value: +[
+  "2020-01-01",
+  "2024-06-30"
+]

First observedApr 15, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses that an API key is required and that anonymous calls fail with subscription_required plus a subscribe link — a concrete failure mode an agent can act on.

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 purpose and then the access constraint. The slug enumeration duplicates the schema, which is mild redundancy, but it is not padding.

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?

An output schema exists, so return values need not be described, and the auth requirement plus slug universe are provided. The main remaining gap is unspecified default behavior when indicator/symbol or dates are omitted, which for a 0-required-param tool would help an agent call 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% and every parameter (symbol, indicator, start_date, end_date) is documented in the schema, so the description adds little parameter-level meaning. It only restates the indicator slug list and urges use of exact slugs, which is already in the schema. 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?

States a specific verb and resource: 'Get historical price series for supported commodity indicators.' The 'historical' scope implicitly separates it from latest_commodities, and the slug list makes the coverage concrete. It never names the sibling alternatives explicitly, so it stops short of a 5.

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?

Usage context is implied by 'historical price series' and the supported-slug list, and the API-key requirement is stated. However, there is no explicit guidance on when to pick this over latest_commodities or commodities_visual_artifact, and no stated defaults for the optional date/indicator parameters.

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

All FXMacroData 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.