MCP Tool
Transmission projects
MISO Long-Range Transmission Plan projects.
- MCP
- Read-only
- Updated
Declaration
transmission_projects(
state?: string,
status?: string,
query?: string,
min_kv?: integer,
tranche?: string,
limit?: integer
)Parameters
statestringOptional- Two-letter state code(s), comma-separated, e.g. 'MN' or 'IA,IL'.
statusstringOptional- complete, in-progress, planned, tbd or any (default). Free text such as 'permitting' or 'approved' maps to in-progress.
querystringOptional- Substring of the project name (substations), status text or developer, e.g. 'Lakefield' or 'ITC'.
min_kvintegerOptional- Minimum voltage in kV (e.g. 765).
tranchestringOptional- LRTP tranche: T1, T2.1 or any.Allowed:
T1,T2.1,anyDefault:any limitintegerOptional- Rows to return (max 50).Default:
50
Return Value
Returns {summary, total, total_cost_m, total_miles_recorded, rows_without_miles, by_tranche, by_status, filters, results, source, url, caveats}: results holds up to limit rows ordered by tranche then cost, with cost_m a MISO planning estimate in $M and developer_source = "status text" when the developer was read from the status text.
Discussion
MISO Long-Range Transmission Plan (LRTP) projects: Tranche 1 (18 projects, 345 kV, about $10.2B) and Tranche 2.1 (24 projects, 345 kV and 765 kV, about $21.8B) across the MISO footprint.
Each row gives its Load Factor ID (gi_uid, when assigned), the tranche, name (endpoint substations), kV, MISO cost estimate ($M), miles (Tranche 1 only), states, target in-service date, status category (complete, in-progress, planned, tbd) with the status text, and the selected or incumbent developer when known. Totals (count, cost, miles) cover all matching rows. Filter by state, status, kV, tranche or a name/developer search.
Returns {summary, total, total_cost_m, total_miles_recorded, rows_without_miles, by_tranche, by_status, filters, results, source, url, caveats}: results holds up to limit rows ordered by tranche then cost, with cost_m a MISO planning estimate in $M and developer_source = "status text" when the developer was read from the status text. Status text is curated and undated; there is no paging beyond 50 rows.
This is the only transmission-plan dataset in Load Factor: other ISOs' plans (PJM RTEP, SPP ITP, ERCOT, CAISO TPP) are not covered, and the caller needs MISO in their permissions. For lines near a site in PJM use grid_context.
Example
Ask your assistant:
Which MISO long-range transmission projects are in Iowa?
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": "transmission_projects",
"arguments": {
"state": "IA"
}
}
}Availability
Listed to accounts with the Transmission, Map or Developer Tracker module. Serves MISO data only, so it is hidden from accounts without MISO access. Results follow your Load Factor permissions (ISOs, detail level, evidence depth and rows per call). See Access & permissions.