FXMacroData

Commodity Indicators

commodities

Read-only

Get historical price series for supported commodity indicators using the exact slugs advertised by this schema. Supported indicators: crude_oil_inventories, distillate_inventories, gasoline_inventories, gold, natural_gas, natural_gas_storage, oil_brent, oil_wti, platinum, silver. Access: API key required, else returns subscription_required with a subscribe link.

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

Input Schema

Name	Required	Description
`latest`	No	Set true for one snapshot of the latest stored value of every commodity indicator; `indicator` is then not needed.
`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, distillate_inventories, gasoline_inventories, gold, natural_gas, natural_gas_storage, oil_brent, oil_wti, platinum, silver.
`start_date`	No	Inclusive lower bound, YYYY-MM-DD.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedNov 5, 2026

removedInput schema / properties / end_date / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / end_date / default
```
Removed value: -null
```

changedInput schema / properties / end_date / examples

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

addedInput schema / properties / end_date / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / indicator / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

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

removedInput schema / properties / start_date / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / start_date / default
```
Removed value: -null
```

changedInput schema / properties / start_date / examples

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

addedInput schema / properties / start_date / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / symbol / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / symbol / default
```
Removed value: -null
```
addedInput schema / properties / symbol / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedInput schema / title
```
Removed value: -"commoditiesArguments"
```

Changed1 schema field changedOct 31, 2026

addedInput schema / properties / latest

Added value: +{
+  "default": false,
+  "description": "Set true for one snapshot of the latest stored value of every commodity indicator; `indicator` is then not needed.",
+  "type": "boolean"
+}

Changed3 schema fields changedOct 22, 2026

changedInput schema / properties / indicator / description

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

changedInput schema / properties / indicator / examples

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

changedInput schema / properties / symbol / examples

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

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.6/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 genuinely new behavior: an API key is required and without it the call returns `subscription_required` with a subscribe link, which tells the agent how failure manifests and points to subscribe_for_mcp_access. It stops short of noting date-range defaults or pagination.

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?

Two front-loaded sentences: capability first, then access constraints, with the slug list as a scannable enumeration. The slug list is duplicated from the schema and eats most of the length, but it is the authoritative accepted vocabulary and reads efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 no explanation, and the auth behavior is a useful addition. Yet for a tool whose 5 parameters include a mode-switching `latest` flag and a legacy `symbol` alias, the description omits both modes, leaving the agent to discover the snapshot path only from the schema.

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 each parameter is already documented, and the description's slug enumeration largely repeats the `indicator` property description rather than adding meaning. It adds no guidance on the `latest` flag, the `symbol` alias, or date-bound interaction, so 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') and enumerates the exact slugs, which cleanly separates it from generic siblings like indicator_query or cot_data. However, calling it purely 'historical' undersells the tool, since the schema exposes a `latest` snapshot mode the description never mentions.

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 is implied: use this for commodity indicator series, passing the advertised slugs. There is no explicit when-to-use/when-not guidance versus siblings such as indicator_query, data_catalogue, or official_datasets, and no mention of how to choose between the historical series and the `latest` snapshot path.

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.

Commodity Indicators

Tool call template

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources