Skip to main content
Glama

FindEnergyRates Electricity Rates

electricity_list_utilities

Read-onlyIdempotent

Use this when someone asks which electric utilities or Texas delivery companies we have plans for in a state, or when you need the exact utility name to pass to electricity_search_plans or electricity_get_price_to_compare. Returns each utility with its current plan count, the newest data date, whether a price to compare is held, and the other names electricity_find_utility_by_zip may use for it (zip_lookup_names). Do not use it to find the utility for a ZIP code (use electricity_find_utility_by_zip). status no_data_for_scope means we hold no utilities for that state, never that it has none.

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>"
    },
    "name": "electricity_list_utilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter US state code, e.g. 'TX', 'OH'. Required.

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?

Annotations cover the safety profile (readOnly, idempotent, closed-world), so the bar is lower, yet the description still adds substantive behavior: the returned per-utility fields (plan count, newest data date, price-to-compare flag, zip_lookup_names) and the critical status semantics that `no_data_for_scope` means we hold no data rather than the state having no utilities.

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?

Front-loaded with the triggering condition and tight throughout; each sentence carries distinct information (use case, return shape, exclusion, status caveat). Slightly dense in the enumeration of returned fields, but no filler.

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?

No output schema exists, and the description compensates by enumerating the returned fields and explaining the no-data status semantics, plus naming the sibling alternatives. An agent has everything needed to call it correctly and interpret the result.

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?

Only one parameter with 100% schema description coverage, so the schema already documents the two-letter state code. The description reinforces the 'in a state' scoping but adds no format or validation detail beyond the schema. Baseline 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?

States a specific verb+resource ('list the electric utilities we cover in a state') and immediately contrasts it with the sibling it is not: 'Do not use it to find the utility for a ZIP code (use electricity_find_utility_by_zip).' An agent can separate it from search_plans, get_price_to_compare, and find_utility_by_zip from the text alone.

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?

Gives explicit trigger conditions ('when someone asks which utilities... we have plans for'), an explicit exclusion with the correct alternative named, and even describes downstream routing ('the exact utility name to pass to electricity_search_plans or electricity_get_price_to_compare'). Nothing 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