Skip to main content
Glama

FindEnergyRates Electricity Rates

electricity_compare_my_plan

Read-onlyIdempotent

Use this when someone gives the rate they pay now and asks whether they could pay less, or how much they would save by switching. Returns how many current plans for their utility are cheaper at their monthly usage, the cheapest of them with estimated monthly and yearly savings, and the utility's price to compare where one exists. In Texas current_rate_cents is the all-in average price per kWh (total bill divided by kWh, delivery included); elsewhere it is the supply (generation) rate per kWh. Savings are estimates at a flat monthly usage, ranked by price only. Do not use it to switch or sign anyone up: it only compares. Plans that pay FindEnergyRates on enrollment are marked referral: true. This never affects ranking. Do not present a plan with bill_credit: true or anchor_shape 'v' as the cheapest or best plan: its price depends on usage. When you mention one, give all three of its disclosed prices (disclosed_avg_500_cents, disclosed_avg_1000_cents, disclosed_avg_2000_cents, the ones it discloses). Ask for the user's monthly usage before recommending any plan. status no_data_for_scope means our data does not cover that market right now, never that it has no plans.

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": {
      "state": "<state>",
      "utility": "<utility>",
      "current_rate_cents": "<current_rate_cents>"
    },
    "name": "electricity_compare_my_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter US state code. Required.
utilityYesThe electric utility (in Texas, the delivery company), as electricity_list_utilities or electricity_find_utility_by_zip names it. Required.
usage_kwhNoMonthly use in kWh from the bill. Optional; 1000 is assumed and said so.
term_monthsNoOnly compare plans of this contract length. Optional.
current_rate_centsYesThe user's current rate in cents per kWh, e.g. 14.2. Texas: all-in average (bill total / kWh). Elsewhere: the supply rate. Required.
current_monthly_fee_dollarsNoOutside Texas only: the user's current supplier's fixed monthly charge, if any. Texas all-in rates already include fees. Optional, default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses return contents, flat-usage estimation behavior, price-only ranking, how referral flags never affect ranking, caveats around bill_credit and anchor_shape 'v' plans, and the meaning of status 'no_data_for_scope'. This is rich behavioral context an agent could not infer from annotations alone.

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 long but front-loaded: purpose and return shape come first, followed by usage caveats. Every sentence carries operational value, though the density of caveats makes it slightly heavy compared with a tighter definition.

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 six-parameter tool with no output schema, the description covers what is returned, how savings are estimated, rate semantics, and important edge cases like referral flags and usage-dependent pricing. Nothing critical to correct invocation appears missing.

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 description coverage is 100%, so the baseline is 3. The description adds real value by clarifying that current_rate_cents means an all-in average in Texas but a supply rate elsewhere, and it reinforces the flat monthly usage assumption behind savings estimates.

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 states a specific verb and resource: comparing a user's current rate against available plans and returning savings estimates. It clearly distinguishes itself from switching/signup tools, so an agent can tell what it does without opening the 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?

It gives a precise trigger ('when someone gives the rate they pay now and asks whether they could pay less') and an explicit exclusion ('Do not use it to switch or sign anyone up'). It also instructs asking for monthly usage before recommending. It stops short of naming a sibling tool as the alternative for browsing plans, but the when/when-not guidance is strong.

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