MCP Tool
Get project dossier
Full dossier for one renewable queue project: who is developing it, how sure Load Factor is, and why.
- MCP
- Read-only
- Updated
Declaration
get_project(
project_number: string,
iso?: string,
sections?: string[],
detail?: string
)Parameters
project_numberstringRequired- Queue ID exactly as
search_projectsreturns it, e.g. J4196, 23INR0103, AE2-189, GEN-2017-036, 0766 (the typed id fromsearch, project:J4196, also works). isostringOptional- Optional ISO hint when the same ID exists in two ISOs (e.g. NYISO 0010 vs CAISO 10).
sectionsstring[]Optional- Sections to include (default all): overview, evidence_summary, plant, ppa, permits, deals_news, analyst_notes, context, sec_parent. A single name or a comma-separated string also works.Allowed:
overview,evidence_summary,plant,ppa,permits,deals_news,analyst_notes,context,sec_parent detailstringOptional- concise (default) = short text and top rows; detailed = longer text, more rows and extra fields (resolution_status, all analyst-note sections).Allowed:
concise,detailedDefault:concise
Return Value
Returns {summary, project_number, iso, url, detail, sections, one key per section, freshness, caveats}.
Discussion
Sections (default all): overview (queue fields; developer, interconnection customer (SPV) and owner as named on record; confidence with its meaning; the records it rests on; coordinates and their accuracy), evidence_summary (active evidence by source and source family, named as in the Load Factor web app, with each record's strength (Strong, Supporting or Lead), top items, which items support the resolved developer), plant (the EIA plant linked to the project), ppa (FERC EQR contract parties linked to the project, plus the ISO-wide bilateral price benchmark for the project's sector over the latest 4 quarters, computed exactly like ppa_price_benchmarks), permits, deals_news (matched deals, news about the linked plant), analyst_notes (AI-generated), context (county peers, same-POI projects, developer portfolio size), sec_parent (the reviewed SEC parent: the registrant that reported the project's company as a subsidiary, with the fiscal years, form and filing link as url; owner as of fiscal year-end; not the developer; shown when your plan includes ownership details for the ISO).
Returns {summary, project_number, iso, url, detail, sections, one key per section, freshness, caveats}. overview.developer_confidence is confirmed (two sources agree), developer_of_record (named in the queue), inferred or unknown (not identified); only confirmed rests on two independent strong records. The plant link is inferred, not reviewed. caveats flags approximate (bucketed) MW in West, Southeast and CAISO, PJM capacity (CIR) MW and superseded PJM rows; freshness dates the data.
Pass the queue ID as search_projects returns it, or the typed id from search (project:J4161); zero-padding variants are tried and iso disambiguates IDs that exist in two ISOs. detail='detailed' returns longer text and more rows. Use get_project_evidence to page through every evidence row; use search_projects to find the ID first.
Example
Ask your assistant:
Who is developing queue project J1229, how sure is Load Factor, and why?
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_project",
"arguments": {
"project_number": "J1229",
"detail": "detailed"
}
}
}Availability
Listed to accounts with the Developer Tracker or Map module. Results follow your Load Factor permissions (ISOs, detail level, evidence depth and rows per call). See Access & permissions.