DOE Energy Information

get_state_energy_profile

Get a comprehensive energy profile for a US state from the EIA.

Returns an overview of energy production, consumption, prices, and
expenditures across all fuel types for the specified state. Useful for
understanding a state's full energy landscape.

Args:
    state: Two-letter US state abbreviation (e.g. 'CA', 'TX', 'NY').

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "get_state_energy_profile"
  }
}

Input Schema

Name	Required	Description	Default
`state`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 3, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations, the description must carry the burden of behavioral disclosure. It does disclose the return scope (production, consumption, prices, expenditures across fuel types), but does not mention potential limitations, data sources beyond EIA, or any edge cases. It provides a reasonable overview but not comprehensive detail.

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 appropriately sized: a clear opening sentence, a brief summary of what's returned, and a parameter format explanation. It is front-loaded with the main purpose and every sentence adds value. No wasted words.

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?

Given the tool's simplicity (one parameter, no nested objects) and the presence of an output schema (which likely defines return values), the description covers the essential context: the purpose, the data scope, and the parameter format. It could mention EIA-specific caveats, but overall it is complete enough for a competent agent.

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

Parameters5/5

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

The input schema has 0% coverage, leaving the 'state' parameter entirely unexplained. The description fully compensates by specifying the format: 'Two-letter US state abbreviation (e.g. 'CA', 'TX', 'NY').' This is essential information that makes the parameter usable.

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 verb 'Get' and the specific resource ('comprehensive energy profile for a US state from the EIA'). It explicitly distinguishes itself from sibling tools (get_electricity_data, get_natural_gas_data, get_petroleum_data) by covering all fuel types instead of a single one.

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?

It provides a clear usage context: 'Useful for understanding a state's full energy landscape.' It implies when to use this tool (when a comprehensive overview is needed), but does not explicitly mention alternatives or when not to use it. This is still better than vague guidance.

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

All DOE Energy Information 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.

Resources

Need Help?