Eia

Eia Ethanol

eia_ethanol

Read-onlyIdempotent

Get fuel ethanol production volumes, stocks, and imports. Returns time series for ethanol supply chain metrics.Key energy-agriculture intersection: most US ethanol is made from corn. Uses EIA petroleum supply data filtered for ethanol (EPOOXE product code).

Input Schema

Name	Required	Description
`end`	No	End date (optional)
`start`	No	Start date (optional)
`series`	Yes	Ethanol data type: "production", "stocks", "imports"
`_apiKey`	Yes	EIA API key
`frequency`	No	Frequency: "weekly", "monthly" (optional, defaults to weekly)

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	Ethanol series type with 'ethanol_' prefix
`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": "production"
-  },
-  {
-    "_apiKey": "your-eia-api-key",
-    "frequency": "weekly",
-    "series": "stocks",
-    "start": "2024-01-01"
-  }
-]New value: +[
+  {
+    "series": "production"
+  },
+  {
+    "frequency": "weekly",
+    "series": "stocks",
+    "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": "Ethanol series type with 'ethanol_' prefix",
+      "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": "production"
+  },
+  {
+    "_apiKey": "your-eia-api-key",
+    "frequency": "weekly",
+    "series": "stocks",
+    "start": "2024-01-01"
+  }
+]

First observedApr 22, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description adds genuine context beyond that: the underlying source (EIA petroleum supply data, EPOOXE product code). It does not cover rate limits, API-key/auth expectations, or freshness/lag, which would have raised the score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three short sentences, front-loaded with what is returned, then the differentiation context. Little waste; 'Returns time series for ethanol supply chain metrics' is slightly redundant but harmless.

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-value explanation is unnecessary, and the description covers purpose, source, and scope. It stops short of operational detail (date formats, data lag), but nothing essential for calling the tool is missing.

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 baseline is 3. The description restates the series options and the weekly default, which duplicates schema content rather than adding format or semantic detail (e.g., date format for start/end).

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 (Get) and precise resource (fuel ethanol production volumes, stocks, imports) with the return shape (time series). The EPOOXE/petroleum-supply note helps differentiate it from sibling eia_petroleum, but it never explicitly says when to prefer eia_petroleum or eia_series instead.

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: agents can infer this is for ethanol-specific supply-chain metrics. However, there is no explicit when-to-use/when-not guidance relative to eia_petroleum or eia_series, so the agent must infer the boundary.

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.