MCP Tool
Grid context near a project or point
Grid infrastructure and market context around one queue project or a latitude/longitude point.
- MCP
- Read-only
- Updated
Declaration
grid_context(
project_number?: string,
latitude?: number,
longitude?: number,
iso?: string,
radius_miles?: number,
include?: string[],
include_line_paths?: boolean
)Parameters
project_numberstringOptional- Queue project ID (e.g. J1229, 23INR0103, AE2-189, or project:J1229 from search). Use this OR latitude+longitude.
latitudenumberOptional- Point latitude (decimal degrees).
longitudenumberOptional- Point longitude (decimal degrees, negative for the western hemisphere).
isostringOptional- Market for a lat/lon point: PJM, MISO, ERCOT, SPP, CAISO, NYISO, ISO-NE, West or WEIM. Default: inferred from the queue projects in the point's county, else the nearest precisely placed pricing node. A project always uses its queue ISO.
radius_milesnumberOptional- Search radius for substations and lines (miles). In project mode with distance bands it is rounded up to 5, 10, 25, 50 or 100.Default:
25 includestring[]Optional- Sections: substations, lmp_nodes, lines, zone (a list or a comma-separated string). Default: all.Allowed:
substations,lmp_nodes,lines,zone include_line_pathsbooleanOptional- Add each PJM line's path coordinates (larger output; point mode, or admins in project mode).Default:
false
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
Returns, within radius_miles (default 25): the nearest OpenStreetMap substations (plus PJM, NYISO or ISO-NE system-map substations with kV for those ISOs); for a project, the real substation its point of interconnection names, when one is found; the nearest 8 LMP pricing nodes of the same market (within 100 mi, precisely placed nodes first) with their day-ahead and real-time price at the last loaded interval, energy/congestion/ loss components and a 24-hour day-ahead summary (West/WEIM locations get a balancing-area price summary instead, because WEIM nodes are centroid-placed); PJM transmission lines nearby (voltage, owner, endpoints); and the ISO load zone. Distances are straight-line miles.
A project uses its queue ISO. A bare point's market is inferred from the queue projects in its county (else the nearest precisely placed pricing node) and the answer says how; pass iso to set it. Load zones come from an unverified county-to-zone map or the nearest pricing node, and are labelled.
Every answer warns when the project location is approximate, when the coordinates fall outside the queue's county, or when the nearest node is far. LMP prices are a one-day snapshot with the interval time and a stale flag; PJM has nodes but no prices; prices and nodes need the LMP module. Project mode follows the caller's plan: restricted viewers (priority projects only) get distance bands instead of miles, and non-admins get no feature coordinates (use a latitude/longitude point for those). Use lmp_snapshot for ISO-wide price rankings, get_project for the developer dossier.
Example
Ask your assistant:
What substations and pricing nodes are near queue project J1229?
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": "grid_context",
"arguments": {
"project_number": "J1229"
}
}
}Availability
Listed to accounts with the LMP Tracker or Map module. Results follow your Load Factor permissions (ISOs, detail level, evidence depth and rows per call). See Access & permissions.