Eia

Eia Electricity

eia_electricity

Read-onlyIdempotent

Get EIA electricity data for a named series (generation, retail_sales, prices, state_generation). Returns time series with period and value across fuel sources and regions. Requires free EIA API key.Covers coal, natural gas, nuclear, hydro, wind, and solar generation.

Input Schema

Name	Required	Description
`end`	No	End date (optional)
`start`	No	Start date (optional)
`series`	Yes	Data series: "generation", "retail_sales", "prices", "state_generation"
`_apiKey`	Yes	EIA API key
`frequency`	No	Frequency: "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
`series`	Yes	Electricity 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": "generation"
-  },
-  {
-    "_apiKey": "your-eia-api-key",
-    "frequency": "monthly",
-    "series": "retail_sales",
-    "start": "2023-01"
-  }
-]New value: +[
+  {
+    "series": "generation"
+  },
+  {
+    "frequency": "monthly",
+    "series": "retail_sales",
+    "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"
+      ]
+    },
+    "series": {
+      "description": "Electricity 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": "generation"
+  },
+  {
+    "_apiKey": "your-eia-api-key",
+    "frequency": "monthly",
+    "series": "retail_sales",
+    "start": "2023-01"
+  }
+]

First observedApr 22, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds useful context about the shape of the result (time series with period and value across fuel sources and regions) and the auth requirement, but says nothing about rate limits, 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?

Three short sentences, front-loaded with the verb and resource, and the auth requirement is easy to spot. The closing sentence on fuel coverage partially restates 'across fuel sources' from the previous sentence, so there is a little redundancy.

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?

Rich annotations, a full schema, and an output schema mean the description does not need to explain return values, and it doesn't. It still lacks the small but useful operational details — default frequency, date-range behavior, and how it relates to the sibling EIA tools — that a five-parameter aggregator tool would benefit from.

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 the enum values for series and frequency are already documented in the schema. The description repeats the series list and hints at which fuels are covered, but adds no format guidance for start/end or frequency beyond what the schema supplies.

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 EIA electricity data') and enumerates the four series it supports, so the agent knows the scope immediately. Differentiation from the EIA siblings (eia_natural_gas, eia_petroleum, eia_ethanol) is only implied through the word 'electricity' rather than stated.

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 by the resource scope, and the 'Requires free EIA API key' line flags a real prerequisite. However, it never says when to choose this over eia_series or the other fuel-specific EIA tools, and no exclusions or defaults are noted.

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.