Eia

Eia Series

eia_series

Read-onlyIdempotent

Search EIA for any energy data series by route path. Returns historical data points with timestamps and values. Use for specific energy metrics not covered by category tools.(e.g., "petroleum/pri/gnd" for gasoline prices, "natural-gas/pri/sum" for gas prices, "electricity/retail-sales" for electricity, "total-energy/data" for total energy). Returns time series with period, value, and metadata.

Input Schema

Name	Required	Description
`end`	No	End date (optional)
`limit`	No	Max records to return (default: 12, max: 5000)
`route`	Yes	EIA data route path. Common routes: "petroleum/pri/gnd" (gasoline/diesel prices), "petroleum/pri/spt" (crude oil spot prices), "petroleum/stoc/wstk" (petroleum stocks), "petroleum/sum/sndw" (petroleum supply/demand weekly), "natural-gas/pri/sum" (natural gas prices), "natural-gas/stor/sum" (natural gas storage), "electricity/retail-sales" (electricity sales/prices), "total-energy/data" (total energy overview), "coal/shipments" (coal data)
`start`	No	Start date, e.g., "2023-01" for monthly, "2023" for annual (optional)
`_apiKey`	Yes	EIA API key (free from eia.gov)
`frequency`	No	Data frequency: "weekly", "monthly", "quarterly", "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
`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",
-    "route": "petroleum/pri/gnd"
-  },
-  {
-    "_apiKey": "your-eia-api-key",
-    "frequency": "weekly",
-    "limit": 52,
-    "route": "natural-gas/pri/sum",
-    "start": "2023-01"
-  }
-]New value: +[
+  {
+    "route": "petroleum/pri/gnd"
+  },
+  {
+    "frequency": "weekly",
+    "limit": 52,
+    "route": "natural-gas/pri/sum",
+    "start": "2023-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"
+      ]
+    },
+    "total": {
+      "description": "Total number of records available",
+      "type": "number"
+    },
+    "truncated": {
+      "description": "True if more than 100 records available",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "total",
+    "description",
+    "count",
+    "data",
+    "truncated"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-eia-api-key",
+    "route": "petroleum/pri/gnd"
+  },
+  {
+    "_apiKey": "your-eia-api-key",
+    "frequency": "weekly",
+    "limit": 52,
+    "route": "natural-gas/pri/sum",
+    "start": "2023-01"
+  }
+]

First observedApr 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile needs no restating. The description adds only that results are historical time series with timestamps/values/metadata; it says nothing about rate limits, API-key requirements, or how partial/invalid routes behave — notable 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key routing instruction is front-loaded, but the description says the return shape twice ('Returns historical data points with timestamps and values' and 'Returns time series with period, value, and metadata'), and the example list repeats the schema verbatim. Useful content, but with clear repetition.

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?

With an output schema present, the description needn't detail return values, and all six parameters are schema-documented. It supplies the one thing structure can't — which tool to pick — and is complete enough to invoke correctly, missing only operational caveats.

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% and each parameter is documented, including the full route example list and the limit default/max. The description's route examples duplicate the schema's route description rather than adding new syntax or constraints, so baseline 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?

States a specific verb and resource (search EIA for any energy data series) plus the mechanism (route path), and explicitly scopes itself against the category tools: 'Use for specific energy metrics not covered by category tools.' An agent can distinguish this generic route-based lookup from siblings like eia_petroleum or eia_natural_gas without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gives the condition that selects this tool over the category tools ('specific energy metrics not covered by category tools') and backs it with four concrete route examples mapping metrics to paths. It stops short of naming the alternative siblings directly, so the routing is clear but slightly indirect.

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.