eia-energy-mcp-server

Query EIA Route Data

eia_query_route

Read-only

Fetches data from a leaf route with optional facet filters, date range, frequency, and column selection. Use eia_describe_route first to discover valid facet IDs, facet values, column IDs, and frequency codes. Data values are strings in the response (EIA API returns all numeric values as strings, e.g. "9.13"); cast to DOUBLE in SQL when arithmetic is needed. Returns a preview inline and stages nothing by default — one upstream request, whatever total says. Pass stage: true to also page past the preview and stage the accumulated set as a DataCanvas table, then pass the returned dataset name to eia_dataframe_query for SQL. Every dataset a tenant stages lands in the same canvas, so tables from different routes cross-join by name with nothing to thread between calls.

Input Schema

TableJSON Schema

Name	Required	Description
`end`	No	Period end (same format as start).
`sort`	No	Result ordering.
`route`	Yes	Leaf route path (e.g. "electricity/retail-sales", "steo"). Discoverable via eia_browse_routes or eia_search_routes. Leading, trailing, and doubled slashes are stripped, so an EIA-doc spelling like "/electricity/retail-sales/" resolves to the same route.
`stage`	No	Stage the matching rows as a DataCanvas table for SQL (default false). Off, the call makes one upstream request and returns the preview alone. On, the service pages past the preview up to EIA_CANVAS_MAX_ROWS and registers the accumulated rows, returning the handle in dataset — several extra upstream requests and seconds of latency on a large route, so turn it on when moving to analysis, not while exploring. Requires a canvas (CANVAS_PROVIDER_TYPE=duckdb); without one nothing is staged whatever this is set to.
`start`	No	Period start in the route date format (e.g. "2020-01" for monthly, "2020" for annual). Format from eia_describe_route.
`length`	No	Rows in the inline preview (default 100, max 5000 per EIA limit). With stage: true, staging is not bounded by this — it pages past the preview on its own.
`offset`	No	Row offset into the matching set (default 0). An offset at or beyond total returns zero rows.
`columns`	No	Data column IDs to return (reduces payload). Defaults to all. IDs discoverable via eia_describe_route.
`filters`	No	Facet filters keyed by facet ID (e.g. { "stateid": "TX", "sectorid": ["RES", "COM"] }). Use the facets[].id values returned by eia_describe_route as keys here.
`frequency`	No	Aggregation frequency ID (e.g. "monthly", "annual"). Defaults to route default. Valid IDs from eia_describe_route.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	Preview rows. All numeric values are strings per the EIA API (e.g. "9.13"). Cast to DOUBLE in SQL for arithmetic: CAST(value AS DOUBLE). Per-column units appear as {col}-units fields inline in each row. Keys are dynamic column IDs from the EIA route.
`error`	No	Present when the call failed. Absent on success.
`route`	No	The route path queried, in canonical spelling — any leading, trailing, or doubled slashes the input carried are stripped. Reusable verbatim in a follow-up call.
`total`	No	Total matching rows in the EIA dataset for this query (may exceed returned rows when pagination or spillover applies).
`notice`	No	Informational message when the response carries no rows — either zero rows matched the filters (broaden the query) or offset paged past the last row (reduce offset below total).
`dataset`	No	df_<id> table handle for the registered dataset — pass directly to eia_dataframe_query SQL (SELECT ... FROM df_<id>). Present only on a stage: true call against a deployment with a canvas configured; absent otherwise, since nothing was staged. Every dataset a tenant stages shares one canvas, so handles from different routes join directly.
`frequency`	No	Frequency of the returned data.
`appliedEnd`	No	Echo of the end period as applied, when an end was provided.
`totalCount`	No	Total matching rows in the EIA dataset.
`appliedSort`	No	Echo of the result ordering as applied, when a sort was provided — the ordering that decided which rows a capped stage holds.
`date_format`	No	Period format for the returned data (e.g. "YYYY-MM").
`appliedStart`	No	Echo of the start period as applied, when a start was provided.
`appliedLength`	No	Preview row count requested for this call.
`appliedOffset`	No	Row offset applied to the query — the cause when a page comes back empty.
`returnedCount`	No	Rows in this response. When returnedCount < totalCount, use offset or canvas for the rest.
`appliedColumns`	No	Echo of the column projection as applied, when columns were provided.
`appliedFilters`	No	Facet filters applied to the query, when provided.
`effectiveRoute`	No	The route path that was queried.
`returned_count`	No	Number of rows in this response. When returned_count < total, use offset pagination or DataCanvas for the rest.
`appliedFrequency`	No	Echo of the frequency as applied, when a frequency was provided.
`truncation_warning`	No	Upstream advisories forwarded verbatim from EIA's warnings[], joined with '; ' when more than one applies. These describe the inline page — EIA's "incomplete return" entry fires whenever the requested length is under total, at any size — not a 5,000-row ceiling on this response. Absent when the response already accounts for the gap the advisory names (the staged table reaches the last row, notice explains the empty page, or canvas_preview_note places the inline page against total because nothing was staged).
`canvas_preview_note`	No	Human-readable note when total exceeds the inline preview. On a stage: true call it names how many rows actually reached the canvas table, and where in the matching set those rows sit whenever the stage does not start at row 1; when staging also stopped short of total (the EIA_CANVAS_MAX_ROWS cap, or an upstream page that did not return), it says so and gives the offset to resume from. Where staging was not requested it places the inline page against total and names stage: true as the way to get SQL access to the rest; where no canvas is configured at all, staging is unavailable, so it names offset paging and CANVAS_PROVIDER_TYPE=duckdb instead.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedAug 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "route",
+      "data",
+      "total",
+      "returned_count",
+      "frequency",
+      "date_format",
+      "effectiveRoute",
+      "totalCount",
+      "returnedCount",
+      "appliedOffset",
+      "appliedLength"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `route_not_found`: Route does not exist in the EIA taxonomy. `route_not_queryable`: Route is a category node with sub-routes, not a queryable leaf. `invalid_facet`: An unknown facet key was used in filters. `invalid_column`: An unknown data column ID was passed in columns. `invalid_frequency`: An unknown frequency code was passed. `invalid_sort`: A sort entry named a column the route does not sort by. `invalid_period`: start or end was not in a period format the route accepts. `no_data`: Date range is inverted (start is after end). `rate_limited`: EIA rate limit hit (OVER_RATE_LIMIT). Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "route_not_found",
+            "route_not_queryable",
+            "invalid_facet",
+            "invalid_column",
+            "invalid_frequency",
+            "invalid_sort",
+            "invalid_period",
+            "no_data",
+            "rate_limited"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "route",
-  "data",
-  "total",
-  "returned_count",
-  "frequency",
-  "date_format",
-  "effectiveRoute",
-  "totalCount",
-  "returnedCount",
-  "appliedOffset",
-  "appliedLength"
-]

Changed7 schema fields changedAug 6, 2026

changedInput schema / properties / length / description

Previous value: -"Rows in the inline preview (default 100, max 5000 per EIA limit). Canvas staging is not bounded by this — it pages past the preview on its own."New value: +"Rows in the inline preview (default 100, max 5000 per EIA limit). With stage: true, staging is not bounded by this — it pages past the preview on its own."

changedInput schema / properties / route / description

Previous value: -"Leaf route path (e.g. \"electricity/retail-sales\", \"steo\"). Discoverable via eia_browse_routes or eia_search_routes."New value: +"Leaf route path (e.g. \"electricity/retail-sales\", \"steo\"). Discoverable via eia_browse_routes or eia_search_routes. Leading, trailing, and doubled slashes are stripped, so an EIA-doc spelling like \"/electricity/retail-sales/\" resolves to the same route."

addedInput schema / properties / stage

Added value: +{
+  "default": false,
+  "description": "Stage the matching rows as a DataCanvas table for SQL (default false). Off, the call makes one upstream request and returns the preview alone. On, the service pages past the preview up to EIA_CANVAS_MAX_ROWS and registers the accumulated rows, returning the handle in dataset — several extra upstream requests and seconds of latency on a large route, so turn it on when moving to analysis, not while exploring. Requires a canvas (CANVAS_PROVIDER_TYPE=duckdb); without one nothing is staged whatever this is set to.",
+  "type": "boolean"
+}

changedOutput schema / properties / canvas_preview_note / description

Previous value: -"Human-readable note when total exceeds the inline preview. With a canvas configured it names how many rows actually reached the canvas table, and where in the matching set those rows sit whenever the stage does not start at row 1; when staging also stopped short of total (the EIA_CANVAS_MAX_ROWS cap, or an upstream page that did not return), it says so and gives the offset to resume from. With no canvas configured nothing is staged, so it places the inline page against total and names offset paging and CANVAS_PROVIDER_TYPE=duckdb as the ways to reach the rest."New value: +"Human-readable note when total exceeds the inline preview. On a stage: true call it names how many rows actually reached the canvas table, and where in the matching set those rows sit whenever the stage does not start at row 1; when staging also stopped short of total (the EIA_CANVAS_MAX_ROWS cap, or an upstream page that did not return), it says so and gives the offset to resume from. Where staging was not requested it places the inline page against total and names stage: true as the way to get SQL access to the rest; where no canvas is configured at all, staging is unavailable, so it names offset paging and CANVAS_PROVIDER_TYPE=duckdb instead."

changedOutput schema / properties / dataset / description

Previous value: -"df_<id> table handle for the registered dataset — pass directly to eia_dataframe_query SQL (SELECT ... FROM df_<id>). Every dataset a tenant stages shares one canvas, so handles from different routes join directly."New value: +"df_<id> table handle for the registered dataset — pass directly to eia_dataframe_query SQL (SELECT ... FROM df_<id>). Present only on a stage: true call against a deployment with a canvas configured; absent otherwise, since nothing was staged. Every dataset a tenant stages shares one canvas, so handles from different routes join directly."

changedOutput schema / properties / route / description

Previous value: -"The route path queried."New value: +"The route path queried, in canonical spelling — any leading, trailing, or doubled slashes the input carried are stripped. Reusable verbatim in a follow-up call."

changedOutput schema / properties / truncation_warning / description

Previous value: -"Upstream advisories forwarded verbatim from EIA's warnings[], joined with '; ' when more than one applies. These describe the inline page — EIA's \"incomplete return\" entry fires whenever the requested length is under total, at any size — not a 5,000-row ceiling on this response. Absent when the response already accounts for the gap the advisory names (the staged table reaches the last row, notice explains the empty page, or canvas_preview_note places the inline page against total where no canvas is configured)."New value: +"Upstream advisories forwarded verbatim from EIA's warnings[], joined with '; ' when more than one applies. These describe the inline page — EIA's \"incomplete return\" entry fires whenever the requested length is under total, at any size — not a 5,000-row ceiling on this response. Absent when the response already accounts for the gap the advisory names (the staged table reaches the last row, notice explains the empty page, or canvas_preview_note places the inline page against total because nothing was staged)."

Changed2 schema fields changedAug 6, 2026

changedOutput schema / properties / canvas_preview_note / description

Previous value: -"Human-readable note when total exceeds the inline preview — names how many rows actually reached the canvas table, and where in the matching set those rows sit whenever the stage does not start at row 1. When staging also stopped short of total (the EIA_CANVAS_MAX_ROWS cap, or an upstream page that did not return), it says so and gives the offset to resume from."New value: +"Human-readable note when total exceeds the inline preview. With a canvas configured it names how many rows actually reached the canvas table, and where in the matching set those rows sit whenever the stage does not start at row 1; when staging also stopped short of total (the EIA_CANVAS_MAX_ROWS cap, or an upstream page that did not return), it says so and gives the offset to resume from. With no canvas configured nothing is staged, so it places the inline page against total and names offset paging and CANVAS_PROVIDER_TYPE=duckdb as the ways to reach the rest."

changedOutput schema / properties / truncation_warning / description

Previous value: -"Upstream advisories forwarded verbatim from EIA's warnings[], joined with '; ' when more than one applies. These describe the inline page — EIA's \"incomplete return\" entry fires whenever the requested length is under total, at any size — not a 5,000-row ceiling on this response. Absent when the response already accounts for the gap the advisory names (the staged table reaches the last row, or notice explains the empty page)."New value: +"Upstream advisories forwarded verbatim from EIA's warnings[], joined with '; ' when more than one applies. These describe the inline page — EIA's \"incomplete return\" entry fires whenever the requested length is under total, at any size — not a 5,000-row ceiling on this response. Absent when the response already accounts for the gap the advisory names (the staged table reaches the last row, notice explains the empty page, or canvas_preview_note places the inline page against total where no canvas is configured)."

Changed3 schema fields changedAug 6, 2026

addedOutput schema / properties / appliedSort

Added value: +{
+  "description": "Echo of the result ordering as applied, when a sort was provided — the ordering that decided which rows a capped stage holds.",
+  "items": {
+    "additionalProperties": false,
+    "description": "A sort criterion as applied.",
+    "properties": {
+      "column": {
+        "description": "Column ID sorted by.",
+        "type": "string"
+      },
+      "direction": {
+        "description": "Sort direction.",
+        "enum": [
+          "asc",
+          "desc"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "column",
+      "direction"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / canvas_preview_note / description

Previous value: -"Human-readable note when total exceeds the inline preview — names how many rows actually reached the canvas table and, when staging stopped short of total (the EIA_CANVAS_MAX_ROWS cap, or an upstream page that did not return), says so and gives the offset to resume from."New value: +"Human-readable note when total exceeds the inline preview — names how many rows actually reached the canvas table, and where in the matching set those rows sit whenever the stage does not start at row 1. When staging also stopped short of total (the EIA_CANVAS_MAX_ROWS cap, or an upstream page that did not return), it says so and gives the offset to resume from."

changedOutput schema / properties / truncation_warning / description

Previous value: -"Forwarded from EIA's warnings[] when the API warns of truncated results near the 5,000 per-page limit."New value: +"Upstream advisories forwarded verbatim from EIA's warnings[], joined with '; ' when more than one applies. These describe the inline page — EIA's \"incomplete return\" entry fires whenever the requested length is under total, at any size — not a 5,000-row ceiling on this response. Absent when the response already accounts for the gap the advisory names (the staged table reaches the last row, or notice explains the empty page)."

Changed10 schema fields changedJul 31, 2026

removedInput schema / properties / canvas_id

Removed value: -{
-  "description": "DataCanvas ID to register results into. Omit on first call — a new canvas is minted and returned. Pass the returned canvas_id on subsequent calls to accumulate multiple route results into one canvas for cross-route SQL joins.",
-  "type": "string"
-}

changedInput schema / properties / length / description

Previous value: -"Rows to fetch per request (default 100, max 5000 per EIA limit)."New value: +"Rows in the inline preview (default 100, max 5000 per EIA limit). Canvas staging is not bounded by this — it pages past the preview on its own."

changedInput schema / properties / offset / description

Previous value: -"Pagination offset (default 0)."New value: +"Row offset into the matching set (default 0). An offset at or beyond total returns zero rows."

addedOutput schema / properties / appliedLength

Added value: +{
+  "description": "Preview row count requested for this call.",
+  "type": "number"
+}

addedOutput schema / properties / appliedOffset

Added value: +{
+  "description": "Row offset applied to the query — the cause when a page comes back empty.",
+  "type": "number"
+}

removedOutput schema / properties / canvas_id

Removed value: -{
-  "description": "Canvas workspace ID — present when spillover occurred or canvas_id was supplied. Pass to subsequent eia_query_route calls to accumulate datasets.",
-  "type": "string"
-}

changedOutput schema / properties / canvas_preview_note / description

Previous value: -"Human-readable note when total > returned rows, describing how to access the full dataset via canvas SQL."New value: +"Human-readable note when total exceeds the inline preview — names how many rows actually reached the canvas table and, when staging stopped short of total (the EIA_CANVAS_MAX_ROWS cap, or an upstream page that did not return), says so and gives the offset to resume from."

changedOutput schema / properties / dataset / description

Previous value: -"df_<id> table handle for the registered dataset — pass directly to eia_dataframe_query SQL (SELECT ... FROM df_<id>)."New value: +"df_<id> table handle for the registered dataset — pass directly to eia_dataframe_query SQL (SELECT ... FROM df_<id>). Every dataset a tenant stages shares one canvas, so handles from different routes join directly."

changedOutput schema / properties / notice / description

Previous value: -"Informational message when zero rows matched the filters — guidance for broadening the query."New value: +"Informational message when the response carries no rows — either zero rows matched the filters (broaden the query) or offset paged past the last row (reduce offset below total)."

changedOutput schema / required

Previous value: -[
-  "route",
-  "data",
-  "total",
-  "returned_count",
-  "frequency",
-  "date_format",
-  "effectiveRoute",
-  "totalCount",
-  "returnedCount"
-]New value: +[
+  "route",
+  "data",
+  "total",
+  "returned_count",
+  "frequency",
+  "date_format",
+  "effectiveRoute",
+  "totalCount",
+  "returnedCount",
+  "appliedOffset",
+  "appliedLength"
+]

Changed4 schema fields changedJun 13, 2026

addedOutput schema / properties / appliedColumns

Added value: +{
+  "description": "Echo of the column projection as applied, when columns were provided.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / appliedEnd

Added value: +{
+  "description": "Echo of the end period as applied, when an end was provided.",
+  "type": "string"
+}

addedOutput schema / properties / appliedFrequency

Added value: +{
+  "description": "Echo of the frequency as applied, when a frequency was provided.",
+  "type": "string"
+}

addedOutput schema / properties / appliedStart

Added value: +{
+  "description": "Echo of the start period as applied, when a start was provided.",
+  "type": "string"
+}

Changed4 schema fields changedJun 4, 2026

addedOutput schema / properties / notice

Added value: +{
+  "description": "Informational message when zero rows matched the filters — guidance for broadening the query.",
+  "type": "string"
+}

addedOutput schema / properties / returned_count

Added value: +{
+  "description": "Number of rows in this response. When returned_count < total, use offset pagination or DataCanvas for the rest.",
+  "type": "number"
+}

addedOutput schema / properties / total

Added value: +{
+  "description": "Total matching rows in the EIA dataset for this query (may exceed returned rows when pagination or spillover applies).",
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "route",
-  "data",
-  "frequency",
-  "date_format",
-  "effectiveRoute",
-  "totalCount",
-  "returnedCount"
-]New value: +[
+  "route",
+  "data",
+  "total",
+  "returned_count",
+  "frequency",
+  "date_format",
+  "effectiveRoute",
+  "totalCount",
+  "returnedCount"
+]

Changed7 schema fields changedMay 30, 2026

addedOutput schema / properties / appliedFilters

Added value: +{
+  "additionalProperties": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    ]
+  },
+  "description": "Facet filters applied to the query, when provided.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedOutput schema / properties / effectiveRoute

Added value: +{
+  "description": "The route path that was queried.",
+  "type": "string"
+}

addedOutput schema / properties / returnedCount

Added value: +{
+  "description": "Rows in this response. When returnedCount < totalCount, use offset or canvas for the rest.",
+  "type": "number"
+}

removedOutput schema / properties / returned_count

Removed value: -{
-  "description": "Rows in this response. When returned_count < total, use offset or canvas for the rest.",
-  "type": "number"
-}

removedOutput schema / properties / total

Removed value: -{
-  "description": "Total matching rows in the EIA dataset.",
-  "type": "number"
-}

addedOutput schema / properties / totalCount

Added value: +{
+  "description": "Total matching rows in the EIA dataset.",
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "route",
-  "data",
-  "total",
-  "returned_count",
-  "frequency",
-  "date_format"
-]New value: +[
+  "route",
+  "data",
+  "frequency",
+  "date_format",
+  "effectiveRoute",
+  "totalCount",
+  "returnedCount"
+]

First observedMay 25, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description discloses that data values are strings and need casting in SQL, that one upstream request is made by default, and that stage:true pages past the preview and incurs extra latency. It explains the staging side effect and requirement of a canvas. This goes well beyond the readOnlyHint annotation, providing complete transparency about side effects and performance.

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 compact yet information-dense. It front-loads the core purpose, then covers prerequisites, data type quirk, default vs. staging behavior, and integration with downstream tools. Every sentence earns its place with no redundancy or fluff.

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?

For a tool with 10 parameters, nested objects, and an output schema, the description covers all necessary context: prerequisites, behavior for preview and staging, latency implications, data type handling, and routing to eia_dataframe_query. The output schema is present, so return-value explanation is not needed. Nothing an agent needs to invoke correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed parameter descriptions (e.g., route slash stripping, stage behavior, filters keyed by facet ID). The description adds a useful note about data values being strings (relevant to numeric columns) and emphasizes the need to consult eia_describe_route for valid parameter values, but these are not parameter-specific over and above the schema. Since the schema already carries the heavy lifting, a 4 is appropriate for the marginal added context.

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 fetches data from a leaf route with optional facet filters, date range, frequency, and column selection. It distinguishes itself from siblings by mentioning 'leaf route' and the preview/staging behavior, which is distinct from route discovery (browse/search) and route metadata (describe) tools.

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?

It explicitly instructs to 'Use eia_describe_route first to discover valid facet IDs, facet values, column IDs, and frequency codes.' It also explains when to use stage:true ('turn it on when moving to analysis, not while exploring') and directs the user to pass the staged dataset name to eia_dataframe_query for SQL, providing clear routing among siblings.

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

All eia-energy-mcp-server 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.

Query EIA Route Data

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources