MCP Tool
Get plant dossier
Dossier for one EIA power plant, by EIA plant id (from search_plants, a /plant/<id> link, or a search id such as plant:57695).
- MCP
- Read-only
- Updated
Declaration
get_plant(
plant_id: integer,
sections?: string[],
detail?: string
)Parameters
plant_idintegerRequired- EIA plant id (plant_id from
search_plants), e.g. 57695; asearchid such as 'plant:57695' is accepted too. sectionsstring[]Optional- Sections to include. Default: overview, ownership, generators, generation, emissions, grid, queue_links, news. Add financials / nearby, or pass ['all'].Allowed:
overview,ownership,generators,generation,emissions,financials,grid,queue_links,news,nearby,all detailstringOptional- concise (default) = summaries; detailed = per-generator rows, full ownership chain, all financial years, news snippets, similar plants.Allowed:
concise,detailedDefault:concise
Return Value
Returns {summary, plant, one key per section with data, sections_without_data, data_as_of, caveats}.
Discussion
Sections (choose with sections; default is all except financials and nearby): overview (location, technologies, capacity factor, description, links; coordinates are rounded to 1 decimal for non-admins when the plant is linked to a queue project in their ISOs); ownership (EIA operator and owners, Wikidata owner and operator); generators (by technology: count, MW, status, years, tracking/bifacial, turbines, battery MWh; individual units in detailed mode; planned retirements); generation (last 24 months of EIA-923 output + annual totals); emissions (CO2/NOx/SO2 2018-2023); financials (PPA price, LCOE, capex/opex by year with source and confidence, FERC price checks); grid (nearest LMP node, hub, balancing authority, substation); queue_links (renewable, non-withdrawn interconnection-queue projects matched to this plant, limited to your permitted ISOs, one row per queue position, labelled inferred); news (10 newest de-duplicated stories); nearby (closest plants).
Returns {summary, plant, one key per section with data, sections_without_data, data_as_of, caveats}. queue_links is labelled inferred (not proof the project is this plant); its rows give the queue's MW (bucket midpoints in West, Southeast and CAISO, capacity MW in PJM), mw_vs_plant, link_basis and developer_confidence. Financials rows carry source and confidence; FERC EQR prices are the seller's reported sale prices, matched to the plant by seller name. Capped output sets truncated.
Use detail='detailed' for per-generator rows, full ownership chain and more history. Queue project detail itself comes from get_project; lists of plants from search_plants.
Example
Ask your assistant:
Give me the full dossier for EIA plant 57695.
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": "get_plant",
"arguments": {
"plant_id": 57695,
"detail": "detailed"
}
}
}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.