Skip to main content
Glama

get_energy

Get energy prices from the U.S. Energy Information Administration. WTI crude, Brent crude, natural gas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoWeekly data points
seriesNowti_crude (default), brent_crude, natural_gaswti_crude

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided. The description indicates a read operation but does not disclose behavioral details such as data freshness, rate limits, authentication needs, or the format of the returned data. The param description hints that data is weekly, but overall transparency is limited.

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 a single sentence of 13 words, efficiently stating the tool's purpose and key series. No fluff; every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should explain what the tool returns. It does not mention return format (e.g., object, array, fields). This lack of output information reduces completeness for an AI agent.

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% (both parameters have descriptions). The tool description reinforces the series names but does not add significant new meaning beyond what the schema already provides. Baseline of 3 is appropriate.

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', the resource 'energy prices', the source 'U.S. Energy Information Administration', and lists the specific series (WTI crude, Brent crude, natural gas). This distinguishes it from siblings which cover different economic topics like jobs, inflation, treasury, etc.

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?

The description implies usage for retrieving energy prices but does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or contexts where other tools would be preferred. No guidance on prerequisites or limitations.

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