Skip to main content
Glama

Open Natural Gas: Georgia natural gas rates

Georgia gas rate history

rate_history
Read-onlyIdempotent

Use this when someone asks how Georgia natural gas rates have changed over time, whether gas prices in Georgia are going up or down, what gas cost last winter or in a past year, or how one marketer's price has moved. Returns month-by-month cheapest and median estimated annual cost for one plan type (fixed = standard 12-month) across the PSC filings Open Natural Gas has published since January 2019, optionally for one marketer. Months that were withheld by the data gate are listed, not skipped silently. Do not use for this month's prices or ranking (use compare_rates), forecasts of future rates, electricity, Liberty Utilities or city/municipal gas systems (use lookup_georgia_gas_provider), other states, or wholesale/Henry Hub prices.

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": "rate_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast month, YYYY-MM (for example 2026-10); omit to end at the latest published month
fromNoFirst month, YYYY-MM (for example 2025-01); omit to start at the earliest published month, 2019-01
marketerNoLimit to one marketer, by name as it appears in compare_rates results (partial names match); omit for the whole market
plan_typeNofixed = standard 12-month fixed (default), variable, senior, or prepayfixed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile needs no restating. The description adds real behavioral context beyond them: the return content (cheapest and median estimated annual cost per month), the fixed=standard 12-month definition, the January 2019 coverage floor, and the notable disclosure that data-gate-withheld months are listed rather than silently skipped. It stops short of describing value precision or whether the annual-cost figures are estimates versus filed values, which keeps it below a 5 given there is no output schema.

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?

Dense but front-loaded: positive triggers first, then scope/return behavior, then a compact exclusion list. Two sentences total, though the opening trigger sentence is long and could be trimmed slightly without losing routing signal.

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

Completeness5/5

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

For a read-only filtered time-series query with no output schema and zero required parameters, the definition supplies everything an agent needs: what is returned, the coverage window, default plan type, optional marketer filter, the withheld-month behavior, and a clear set of negative cases. No material gap remains.

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%, including YYYY-MM patterns, defaults, and the enum values, so the schema already carries parameter meaning and the baseline is 3. The description reinforces the plan_type definition and the optional single-marketer filtering, but adds no format or behavior detail the schema lacks.

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+resource+scope: month-by-month cheapest and median estimated annual cost for one plan type across PSC filings since January 2019, optionally for one marketer. It also names the sibling it is not (compare_rates) so an agent can distinguish intent without opening either schema.

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

Usage Guidelines5/5

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

Explicit when-to-use triggers are enumerated (rate trend over time, direction of prices, cost last winter, one marketer's price movement), and four exclusion categories are given with the alternative tool named for two of them (compare_rates for current prices/ranking, lookup_georgia_gas_provider for Liberty/city systems). Little 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.

Resources