MCP Tool
Find companies / name variants
Resolve a company name to the exact name variants Load Factor holds.
- MCP
- Read-only
- Updated
Declaration
find_companies(
name: string,
iso?: string,
limit?: integer
)Parameters
namestringRequired- Company name or fragment, e.g. 'NextEra', 'Invenergy', 'Savion'. Case-insensitive; 2+ characters.
isostringOptional- Limit to one ISO/region (or comma-separated list): PJM, MISO, ERCOT, SPP, CAISO, NYISO, ISO-NE, West, Southeast, IESO, AESO, Maritimes, Quebec, BC, Saskatchewan, Manitoba. Default: every ISO your Load Factor plan covers.
limitintegerOptional- Variants to return (max 30).Default:
15
Return Value
Returns {summary, query, scope, results, next_step, caveats}: each results row is one stored variant with name, match (how it matched the query), roles and the non-zero counts above.
Discussion
Resolve a company name to the exact name variants Load Factor holds. Names are fragmented: 'NextEra Energy Inc' vs 'NextEra Energy Resources' vs project SPVs ('NextEra Energy Bluff Point, LLC'), typos, and joint strings ('A; B'). This searches every place a company name appears in Load Factor (queue records, operating plants, FERC market filings, deals and state business records) and returns one row per variant (case-insensitive) with its roles and counts: live renewable queue projects and MW within your ISO permissions, total queue projects, operating EIA plants and MW, FERC seller / buyer quarters, and deals. Ranked exact > prefix > whole word > substring, then by project count. Matching ignores accents ('Orsted' finds 'Ørsted') and lowercase d/s letters that some stored names lost ('Madison Energy Holdings' finds 'Maion Energy Holing LLC', flagged match='ds_variant').
Rows carry cik and sec_name when a Load Factor analyst reviewed the name's link to an SEC EDGAR registrant (get_company_profile's sec section, fetch company:cik:<n> or sec_company_filings / sec_company_subsidiaries then give the SEC data).
Returns {summary, query, scope, results, next_step, caveats}: each results row is one stored variant with name, match (how it matched the query), roles and the non-zero counts above. Queue counts cover every developer confidence level, not only where two sources agree; a queue developer inferred from an EIA plant record is often the utility or parent, not the developer.
Use it first for any "who is X / what does X have" question, then pass the chosen variants to get_company_profile(names=[...]). For a filtered project list use search_projects(developer=...).
Example
Ask your assistant:
What company name variants and SPVs does Load Factor hold for NextEra in ERCOT?
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": "find_companies",
"arguments": {
"name": "NextEra",
"iso": "ERCOT"
}
}
}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.