Skip to main content
Glama
Sign In

energyai

by com.energyaisolution
OverviewDiscussionsAdmin

energy_calendar

Energy Odds (paper mode): upcoming target dates for three public EIA numbers (US retail gasoline weekly, US commercial crude inventories weekly, Henry Hub weekly high/low), EIA release timing, and whether a forecast is already logged for each date. Free. [always free — no API key required]

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
apiKeyNoOptional existing EnergyAI key for hosts that cannot change Authorization headers. Use it to retain account identity for discovery and get_builder_upgrade_link after a trial. Removed before tool execution and persistence. Omit when the Bearer header is attached; never show the key to the user.
seriesNoOptional: one series. Omit for all three.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It helpfully states that the tool is free and requires no API key, but it leaves 'paper mode' and 'Energy Odds' unexplained and does not explicitly confirm read-only behavior or absence of side effects.

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?

The description is compact and front-loads the core content: dates, timing, and forecast-logged status. The 'Free.' sentence and bracketed no-API-key note are slightly redundant, and the unexplained 'Energy Odds (paper mode)' prefix adds mild clutter.

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

Completeness3/5

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

For a simple two-parameter, no-output-schema listing tool, the description covers the main content and the free-access condition. However, it does not explain what 'paper mode' means or how this calendar relates to the sibling forecasting and verification tools, leaving gaps an agent must infer.

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 both the optional apiKey and series parameters are already well documented in the schema. The description lists the three series names, which reinforces the enum but adds no syntax or behavior beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource: upcoming EIA target dates for three named series, release timing, and whether a forecast is already logged. That is clear enough to distinguish it from a generic calendar, but it never explicitly names or contrasts with siblings like energy_forecast or energy_track_record.

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

Usage Guidelines2/5

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

The description explains what the tool returns but gives no explicit guidance on when to use it versus alternatives such as energy_forecast or verify_forecast. The only implied use is checking upcoming dates, with no stated exclusions or workflow context.

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

All energyai toolsInspect
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