MCP Tool
Projects advancing to construction
Queue projects, EIA plants and data centers that advanced toward construction.
- MCP
- Read-only
- Updated
Declaration
construction_triggers(
trigger_type?: string[],
iso?: string,
state?: string,
technology?: string,
subject_kind?: string[],
since?: string,
limit?: integer,
offset?: integer
)Parameters
trigger_typestring[]Optional- Trigger types: ia_executed, construction_started, construction_planned, financing_closed, permit_approved, epc_awarded.
isostringOptional- ISO code, e.g. PJM, MISO.
statestringOptional- Two-letter state code.
technologystringOptional- Technology/fuel type.
subject_kindstring[]Optional- queue_project, eia_plant or data_center.
sincestringOptional- Only triggers first seen on or after this date (YYYY-MM-DD).
limitintegerOptional- Rows to return (max 100).Default:
25 offsetintegerOptional- Skip this many rows (paging).Default:
0
Return Value
Structured results that your assistant reads and sums up for you. The rows and the detail follow your Load Factor permissions (see Availability).
Discussion
Queue projects, EIA plants and data centers that advanced toward construction: interconnection agreement executed, construction started, a planned construction start (a start date still ahead, not yet begun), financing closed, permit approved, or EPC awarded. Filter by trigger type, ISO, state, technology, subject kind and dates. Each row names the confirmed EPC and any lender/financier on the deal.
Example
Ask your assistant:
Which PJM queue projects have an executed interconnection agreement?
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": "construction_triggers",
"arguments": {
"trigger_type": [
"ia_executed"
],
"iso": "PJM",
"limit": 10
}
}
}Availability
Listed to accounts with the projects module. Results follow your Load Factor permissions (ISOs, detail level, evidence depth and rows per call). See Access & permissions.