MCP Tool
Data-center site and nearby supply (Load Factor Demand)
One data-center site from Load Factor Demand.
- MCP
- Read-only
- Updated
Declaration
get_data_center(id: string, radius_mi?: number)Parameters
idstringRequired- Site id from
search_data_centers, e.g. osm:way/123456789. radius_minumberOptional- Radius for the queued generation and supply outlook, in miles (default 25, max 50).Default:
25.0
Return Value
Returns {summary, site, radius_mi, queued_nearby, nearest_active_projects, supply_outlook, attribution, caveats}: queued_nearby gives count, MW and by-fuel rows for active, withdrawn and operating projects; nearest_active_projects lists up to 10 with straight-line distance_mi; supply_outlook holds the verdict, yearly demand MW with its demand_source, by_year MW and the grid lines and substations.
Discussion
One data-center site from Load Factor Demand: its record (operator, location, ISO, status, capacity and planned MW, source, Epoch AI build-out figures when Epoch covers it), the renewable and storage queue projects within radius_mi (default 25, max 50) counted by fuel and by status (active, withdrawn, operating), the nearest active projects with their developer and confidence, and the supply outlook the Load Factor app shows: queued MW due online by year, the share expected to finish at historical completion rates, its capacity value against the site's demand, and the nearby transmission lines and substations. An indicative screen, not an interconnection study.
Returns {summary, site, radius_mi, queued_nearby, nearest_active_projects, supply_outlook, attribution, caveats}: queued_nearby gives count, MW and by-fuel rows for active, withdrawn and operating projects; nearest_active_projects lists up to 10 with straight-line distance_mi; supply_outlook holds the verdict, yearly demand MW with its demand_source, by_year MW and the grid lines and substations. Projects are tied to the site by distance, not a named interconnection; a site without coordinates returns only site. Use search_data_centers to find the id.
Example
Ask your assistant:
What generation is queued within 25 miles of this data-center site, and could it cover the site's demand?
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",
"arguments": {
"id": "epoch:google-fort-wayne",
"radius_mi": 25
}
}
}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.