Eia

Eia Natural Gas

eia_natural_gas

Read-onlyIdempotent

Get EIA natural gas time series for a named series (prices, production, consumption, storage, spot_prices). Returns period, value, and area metadata. Requires free EIA API key.Includes Henry Hub spot prices, underground storage, marketed production, and consumption by sector.

Input Schema

Name	Required	Description
`end`	No	End date (optional)
`start`	No	Start date (optional)
`series`	Yes	Data series: "prices", "production", "consumption", "storage", "spot_prices"
`_apiKey`	Yes	EIA API key
`frequency`	No	Frequency: "weekly", "monthly", "annual" (optional)

Output Schema

Name	Required	Description
`data`	Yes	Time series data points (max 100 returned)
`count`	Yes	Number of records returned
`total`	Yes	Total number of records available
`series`	Yes	Natural gas series type requested
`truncated`	Yes	True if more than 100 records available
`description`	Yes	Series description from EIA API

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "_apiKey": "your-eia-api-key",
-    "series": "prices"
-  },
-  {
-    "_apiKey": "your-eia-api-key",
-    "frequency": "weekly",
-    "series": "storage",
-    "start": "2024-01-01"
-  }
-]New value: +[
+  {
+    "series": "prices"
+  },
+  {
+    "frequency": "weekly",
+    "series": "storage",
+    "start": "2024-01-01"
+  }
+]

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of records returned",
+      "type": "number"
+    },
+    "data": {
+      "description": "Time series data points (max 100 returned)",
+      "items": {
+        "properties": {
+          "area": {
+            "description": "Geographic area name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "description": {
+            "description": "Series description",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "period": {
+            "description": "Time period (e.g., date or year)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "process": {
+            "description": "Process or measurement type",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "product": {
+            "description": "Product type",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "units": {
+            "description": "Unit of measurement",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "value": {
+            "description": "Numeric value for the period",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "description": {
+      "description": "Series description from EIA API",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "series": {
+      "description": "Natural gas series type requested",
+      "type": "string"
+    },
+    "total": {
+      "description": "Total number of records available",
+      "type": "number"
+    },
+    "truncated": {
+      "description": "True if more than 100 records available",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "series",
+    "total",
+    "description",
+    "count",
+    "data",
+    "truncated"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-eia-api-key",
+    "series": "prices"
+  },
+  {
+    "_apiKey": "your-eia-api-key",
+    "frequency": "weekly",
+    "series": "storage",
+    "start": "2024-01-01"
+  }
+]

First observedApr 22, 2026

TDQS

A3.8/5.0

Behavior4/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 contribution is the auth prerequisite ('Requires free EIA API key') and a rough return shape (period, value, area metadata). That is real added context, but limits, rate limits, and frequency-dependent behavior of the series are not discussed.

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?

Front-loaded with the core action and the series list. The trailing sentence ('Includes Henry Hub spot prices, underground storage...') largely re-expands the series parenthetical and has a missing space after 'key.', making it slightly redundant and less polished than it could be.

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?

An output schema exists, so return values need not be spelled out, and the schema fully documents all five parameters. The description covers the domain, the series options, and the API-key prerequisite — everything an agent needs 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 coverage is 100%, so the schema already documents series, frequency, start, end and _apiKey. The description restates the series values but adds no semantics on date formats, frequency defaults, or how start/end interact with frequency — so it neither compensates nor detracts.

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?

Specific verb and resource: 'Get EIA natural gas time series for a named series', with the supported series enumerated. The domain (natural gas) implicitly distinguishes it from eia_electricity/eia_petroleum/eia_ethanol, but it never names those siblings or eia_series, so routing is left to the agent's inference.

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 only implied through the series enumeration and the note that a free EIA API key is required. There is no statement of when to prefer this over eia_series or the other EIA domain tools, and no exclusions or prerequisites beyond the key.

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

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