Skip to main content
Glama

Heating Oil and Propane Prices MCP

Get heating fuel price history

get_heating_fuel_price_history
Read-onlyIdempotent

EIA weekly residential heating oil or propane prices per gallon for the US or a surveyed state between two dates (series since 1990 for most areas), with high, low and average. Default is the last 52 weeks.

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": {
      "fuel": "<fuel>"
    },
    "name": "get_heating_fuel_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
fuelYes
stateNoState name or code ("Maine", "CT"), an EIA region ("New England (PADD 1A)") or "US". Default US.
end_dateNoEnd date, default the latest week as YYYY-MM-DD.
start_dateNoStart date as YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered; the description adds substantive context beyond that, including weekly data frequency, the historical depth of the series, the default time window, and the fact that high, low, and average values come back. With no output schema, this return-value summary is particularly valuable. It stops short of describing the exact response shape or ordering.

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?

A single dense sentence that front-loads the data source, frequency, and unit before moving to scope and defaults. Every clause adds information; the parenthetical about the series starting in 1990 earns its place, though the sentence is long enough that the default-window detail would read better as its own short clause.

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 four-parameter read tool with no output schema, the description covers the essentials: what series is returned, the unit, the aggregation statistics, the geographic scope, the historical floor, and the default window. What remains unstated is the response structure and how dates outside the coverage window are handled, which is a modest gap rather than a blocker.

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 75%, so the baseline is 3, and the description adds meaning the schema lacks: start_date has no default in the schema, yet the description establishes that omitting the range yields the last 52 weeks, and it discloses the practical floor of the series (since 1990 for most areas). It also clarifies that state accepts the US or a surveyed state, reinforcing rather than merely repeating the schema's wording.

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?

States a specific verb and resource: EIA weekly residential heating oil or propane prices per gallon, with named dimensions (US or a surveyed state, date range) and return statistics (high, low, average). It does not distinguish itself from the siblings estimate_heating_fuel_cost or get_heating_oil_propane_prices, so an agent must infer that this is the historical series rather than a cost estimate or current-price lookup.

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?

Useful operational context is given implicitly: the default window is the last 52 weeks and coverage reaches back to 1990 for most areas, which tells the agent how far back it may query. There is no explicit when-to-use or when-not-to-use guidance and no mention of the two sibling tools, so routing between historical prices, current prices, and cost estimation is left to inference.

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.