MCP Tool
Search operating power plants
Search EIA power plants (EIA-860/923: built and planned generating plants, not the interconnection queue).
- MCP
- Read-only
- Updated
Declaration
search_plants(
query?: string,
state?: string,
county?: string,
iso?: string,
fuel?: string,
status?: string,
renewable_only?: boolean,
owner?: string,
min_mw?: number,
max_mw?: number,
min_cf?: number,
sort?: string,
limit?: integer,
offset?: integer
)Parameters
querystringOptional- Plant name or EIA operator/utility (substring), or an exact EIA plant id.
statestringOptional- Two-letter state code(s), comma-separated, e.g. 'TX' or 'IA,MN'.
countystringOptional- County name (substring match).
isostringOptional- ISO market(s), comma-separated: MISO, PJM, CAISO, ISO-NE, ERCOT, NYISO, SPP; or 'none' for plants outside those markets (West, Southeast).
fuelstringOptional- Fuel(s), comma-separated (any of them matches): solar, wind, offshore wind, onshore wind, hybrid, storage, hydro, geothermal, biomass, biogas, biofuel, wood, gas, coal, nuclear, oil, diesel, waste, other; queue fuel names ('Battery Storage', 'Offshore Wind', 'Hybrid'); or EIA codes (SUN, WND, MWH, WAT, GEO, NG, BIT, SUB, NUC...).
statusstringOptional- EIA plant status. operating (default); planned / under_construction / testing are EIA-860 plants not yet in commercial operation; all = every status.Allowed:
operating,planned,under_construction,standby,out_of_service,testing,allDefault:operating renewable_onlybooleanOptional- true (default) = renewable primary fuel only; false also returns fossil and nuclear plants.Default:
true ownerstringOptional- Owner/operator name substring, matched against the EIA operator/utility.
min_mwnumberOptional- Minimum plant capacity (MW).
max_mwnumberOptional- Maximum plant capacity (MW).
min_cfnumberOptional- Minimum annual capacity factor, as a fraction (0.25) or percent (25).
sortstringOptional- capacity = largest first (default); co2 = highest latest CO2 first; operating_year = newest first; name = A-Z.Allowed:
capacity,capacity_factor,co2,operating_year,nameDefault:capacity limitintegerOptional- Rows to return (max 100; your plan may cap lower).Default:
25 offsetintegerOptional- Skip this many rows (paging).Default:
0
Return Value
Returns {summary, total, total_mw, by_fuel, offset, next_offset, filters, data_as_of, results, caveats}: results is one page of plants, fuel_legend names the EIA fuel codes in primary_fuel, and next_offset is null on the last page.
Discussion
Filters combine with AND. query matches plant name or EIA operator/utility (substring), or an exact EIA plant id. Defaults: status operating, renewable fuels only (solar, wind, storage, hydro, geothermal, biomass, biogas); set renewable_only=false to include gas, coal, nuclear or oil plants for emissions or M&A context. fuel also takes the queue fuel names search_projects returns ('Battery Storage', 'Offshore Wind', 'Hybrid'): offshore/onshore wind and hybrid (two or more renewable technologies, no fossil unit) are filtered on the EIA-860 technology list. Results include total, total_mw and a by-fuel breakdown computed over every match, so counts and capacity can be reported without paging. Each row has the EIA operator (eia_operator), capacity factor (0-1), latest CO2, its Load Factor ID (gi_uid, when assigned) and a url to cite. Plants are a public EIA reference layer and are not limited to your ISOs; queue projects linked to a plant (get_plant) are.
Returns {summary, total, total_mw, by_fuel, offset, next_offset, filters, data_as_of, results, caveats}: results is one page of plants, fuel_legend names the EIA fuel codes in primary_fuel, and next_offset is null on the last page. A page can hold fewer than limit rows to fit the output size; keep paging from next_offset.
Use this for "largest wind farms in Iowa", "NextEra's operating solar plants in Texas", "coal plants in PJM by CO2". For one plant's full dossier (ownership chain, generators, monthly generation, emissions history, PPA prices, grid node, linked queue projects, news) use get_plant. For interconnection-queue projects (proposed, not yet built) use search_projects.
Example
Ask your assistant:
What are the largest operating renewable power plants in Texas?
It would call the tool with a request like this one (your client builds and sends it for you):
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "search_plants",
"arguments": {
"state": "TX",
"limit": 10
}
}
}Availability
Listed to accounts with the Developer Tracker or Map module. Results follow your Load Factor permissions (ISOs, detail level, evidence depth and rows per call). See Access & permissions.