Skip to main content
Glama

TexasHomeBills — Texas electricity plans

market_wholesale_prices

ERCOT wholesale electricity prices ($/MWh) at trading hubs and load zones: real-time or day-ahead, daily avg/min/max or hourly, with completeness flags. Free (no key or free key): the most recent 30 days of each series; a Pro key unlocks full history. Values are exact as published with unit, date and original source URL; incomplete days are flagged, never filled. Free for non-commercial use with attribution; commercial use requires Pro.

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

Input Schema

NameRequiredDescriptionDefault
endNoYYYY-MM-DD (default: latest date)
limitNoRows to return (default 100)
pointNoComma-separated: HB_HOUSTON, HB_NORTH, HB_SOUTH, HB_WEST, HB_PAN, HB_BUSAVG, HB_HUBAVG, LZ_HOUSTON, LZ_NORTH, LZ_SOUTH, LZ_WEST, LZ_AEN (Austin), LZ_CPS (San Antonio), LZ_LCRA, LZ_RAYBN. Default HB_HOUSTON.
startNoYYYY-MM-DD. Default: 30 days ending at the series' latest date. Older dates need a Pro key.
marketNort = real-time, da = day-aheadrt
offsetNo
granularityNoday

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses tier/rate limits (30 days free), data-integrity guarantees (values exact as published, incomplete days flagged and never filled), and licensing constraints (attribution required, commercial use needs Pro). It omits pagination or response-shape behavior, keeping it short of a 5.

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 paragraph that front-loads what the tool returns before moving to tier and licensing terms. Most sentences earn their place, though the licensing/attribution sentence is more legal boilerplate than task-relevant guidance.

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 7-parameter read tool with no annotations and no output schema, the description covers the key gaps: data semantics, tier limits, integrity handling, and partial return content. It could say more about pagination (limit/offset) and default date behavior, but an agent has enough to call it correctly.

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 71%, and the description meaningfully augments it: 'real-time or day-ahead' clarifies the market enum and 'daily avg/min/max or hourly' explains what day vs hour granularity actually yields beyond the bare enum values. It also conveys units and the presence of completeness flags, adding return-context not in the schema.

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 resource (ERCOT wholesale electricity prices in $/MWh) and scope (trading hubs and load zones), with concrete modes (real-time/day-ahead, daily avg/min/max or hourly). An agent can immediately distinguish it from siblings like market_gas_prices and electricity_price_trends. The verb+resource+scope combination is unambiguous.

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?

It gives useful access conditions — 30-day free window vs Pro for full history — but frames them as pricing tiers rather than when-to-use guidance. It never names an alternative or states when a sibling tool (e.g., electricity_price_trends) would be more appropriate. Usage is implied rather than instructed.

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