MCP Tool
Supply screen per data-center site (Load Factor Demand)
One data-center site's supply screen.
- MCP
- Read-only
- Updated
Declaration
get_data_center_supply_screen(id: string, target_year?: integer)Parameters
idstringRequired- Site id from
search_data_centers, e.g. osm:way/123456789. target_yearintegerOptional- Year the cover is measured for (default: the site's planned year, or 2028).
Return Value
Returns {summary, site, planned_mw, planned_date, target_year, data_as_of, demand_source, radii, linkage, nearest_substation, nearest_lmp_node, nearby_projects, attribution, caveats}: each radii row gives queued_mw, expected_to_finish_mw, capacity_value_mw (floored to 0.1 MW), cover_pct / cover_label (empty without planned MW) and verdict_sentence; nearby_projects lists up to 50 within the widest radius with distance_mi; nearest_lmp_node is a location, not a price.
Discussion
One data-center site's supply screen: for 10, 25 and 50 miles, the queue MW due online by a target year (default: the site's planned year, or 2028), the share expected to finish at historical completion rates, and that share as a floored cover percentage of the site's planned MW; the nearby queue project rows, the nearest substation and LMP node, and the app's own verdict sentence. Queue linkage is proximity-based, never a named interconnection link ("linkage": "proximity"): an indicative screen, not an interconnection study. Withdrawn and operating projects are counted apart and are not supply to come.
Returns {summary, site, planned_mw, planned_date, target_year, data_as_of, demand_source, radii, linkage, nearest_substation, nearest_lmp_node, nearby_projects, attribution, caveats}: each radii row gives queued_mw, expected_to_finish_mw, capacity_value_mw (floored to 0.1 MW), cover_pct / cover_label (empty without planned MW) and verdict_sentence; nearby_projects lists up to 50 within the widest radius with distance_mi; nearest_lmp_node is a location, not a price. Use search_data_centers to find the id.
Example
Ask your assistant:
Could nearby queued supply cover this site's planned MW by 2028?
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_data_center_supply_screen",
"arguments": {
"id": "epoch:google-fort-wayne",
"target_year": 2028
}
}
}Availability
Listed to accounts with the Map module. Results follow your Load Factor permissions (ISOs, detail level, evidence depth and rows per call). See Access & permissions.