Skip to main content
Glama

get_eia_energy_public_snapshot

Read-only

Use when current energy price data is needed for a commodity brief, input cost analysis, or energy sector context in a CFO or investment brief. Returns WTI crude and natural gas spot prices when EIA API is configured. Example: WTI crude $78.40/bbl, natural gas $2.31/MMBtu — energy input costs 12% below year-ago levels, favorable for manufacturing and transportation operating margins. Source: US Energy Information Administration. $0.02 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_eia_energy_public_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely useful non-annotation context — per-call cost ($0.02 USDC), an upstream dependency (EIA API must be configured), and source attribution — but is silent on what happens when the dependency fails and on data freshness/lag.

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?

Front-loaded with the 'Use when' trigger, then the return contents, then an example. The example is long and includes editorial interpretation ('favorable for manufacturing and transportation operating margins') that goes beyond what the tool returns, but it does illustrate output shape and unit conventions.

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?

For a zero-parameter lookup with no output schema, the description supplies return fields, units, source, and cost — enough to call it correctly. The one gap is what the tool returns or does when the EIA API is not configured, which matters because the tool is explicitly conditional on that setup.

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?

Zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The call takes no arguments, which is consistent with the empty object schema.

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?

States a specific verb and resource: returns WTI crude and natural gas spot prices. The narrow, enumerated data set (only two energy benchmarks) makes it distinguishable from siblings like get_agricultural_commodity_benchmark or macro snapshot tools without opening a schema.

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?

Explicit when-to-use framing: 'Use when current energy price data is needed for a commodity brief, input cost analysis, or energy sector context in a CFO or investment brief.' Clear context, but no when-not conditions and no alternatives named for the case where the EIA API is not configured.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources