Skip to main content
Glama

Eia

by io.github.pipeworx-io

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

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd date (optional)
limitNoMax records to return (default: 12, max: 5000)
routeYesEIA 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)
startNoStart date, e.g., "2023-01" for monthly, "2023" for annual (optional)
_apiKeyYesEIA API key (free from eia.gov)
frequencyNoData frequency: "weekly", "monthly", "quarterly", "annual" (optional)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesTime series data points (max 100 returned)
countYesNumber of records returned
totalYesTotal number of records available
truncatedYesTrue if more than 100 records available
descriptionYesSeries description from EIA API

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • 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"
+  }
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds that the tool 'Returns historical data points with timestamps and values' and 'Returns time series with period, value, and metadata,' which provides useful context beyond annotations. No contradictions.

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?

The description is concise at just a few sentences, front-loaded with purpose, and includes helpful examples. Every sentence adds value without repetition.

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?

Given the tool's complexity (6 params, 2 required), 100% schema coverage, and existing output schema, the description sufficiently covers purpose, usage guidelines, and return format. It mentions 'time series with period, value, and metadata,' which is adequate when combined with the output 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 the baseline is 3. The description adds examples of route paths inline, but the schema already contains detailed parameter descriptions, including the route parameter with many examples. The added value is marginal.

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?

The description clearly states the tool's purpose: 'Search EIA for any energy data series by route path.' It distinguishes from sibling category-specific tools by saying 'Use for specific energy metrics not covered by category tools,' and provides concrete examples of route paths.

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

Usage Guidelines5/5

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

The description explicitly tells when to use this tool vs alternatives: 'Use for specific energy metrics not covered by category tools.' This directly guides the agent toward this tool for general series queries and away from category-specific siblings.

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

All Eia toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Several tools occupy nearly identical roles: ask_pipeworx and ask_pipeworx_beta are described as currently identical, ask_pipeworx_grounded and deep_research overlap with the router, and eia_series overlaps with the specialized eia_electricity/eia_ethanol/eia_natural_gas/eia_petroleum tools. The Polymarket opportunity scanners and the two AI-visibility checkers also blur together, making confident tool selection difficult despite detailed descriptions.

Naming Consistency3/5

Most tools follow a snake_case verb-first pattern (remember, recall, forget, resolve_entity, validate_claim), but there are notable deviations: eia_electricity and eia_ethanol are noun-first category names, recent_alerts and recent_changes are adjective-noun, and pipeworx_trending and polymarket_edges are not verb-driven. The eia_ and polymarket_ prefixes add some predictability, so the naming is readable but inconsistent.

Tool Count2/5

At 36 tools, this is well past the heavy threshold and feels like a kitchen-sink aggregation of several separate products rather than one focused server. Many tools could be consolidated: the five eia_* lookups, the multiple ask_pipeworx variants, and the several Polymarket scanners all serve close purposes. A 36-tool surface is too much for an agent to navigate efficiently.

Completeness4/5

Within the major subdomains the set is quite complete: entity research has profile/compare/changes/resolve, memory has remember/recall/forget, subscriptions have subscribe/list/unsubscribe/recent_alerts, and Polymarket analysis has edge discovery, fill-risk, venue-spread, and persistence tracking. Minor gaps exist—no subscription update flow, no dedicated EIA coal/nuclear/renewables series beyond the generic eia_series fallback—but agents can work around them.

Resources