Skip to content
Load Factor Docs
Open Load Factor

MCP Tool

Company profile

One company's footprint across Load Factor for the exact name variants you pass (usually chosen from find_companies; case- and accent-insensitive exact match).

  • MCP
  • Read-only
  • Updated

Declaration

MCP tool
get_company_profile(
    names?: string[],
    name?: string,
    match?: string,
    iso?: string,
    sections?: string[],
    detail?: string
)

Parameters

namesstring[]Optional
Exact name variants (1-15), usually picked from find_companies, e.g. ['NextEra Energy Inc', 'NextEra Energy', 'NextEra Energy Resources']. Case- and accent-insensitive. A single string is taken as one name (never split on commas).
namestringOptional
A single name; with match='contains' every variant containing this text (3+ characters) is merged.
matchstringOptional
exact (default) = names/name must equal a stored variant; contains = substring match on name.Allowed: exact, containsDefault: exact
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.
sectionsstring[]Optional
Sections to include (default: all): queue, plants, ppa, deals_news, entity, sec. A list, or one name / comma-separated string ('queue,plants'); 'all' = every section.Allowed: queue, plants, ppa, deals_news, entity, sec
detailstringOptional
concise (default) = short lists; detailed = longer lists and extra fields.Allowed: concise, detailedDefault: concise

Return Value

Returns {summary, names, match, scope, other_variants, one key per section, caveats}; each section has its own totals, lists and caveats.

Discussion

One company's footprint across Load Factor for the exact name variants you pass (usually chosen from find_companies; case- and accent-insensitive exact match). If other stored variants contain a name you passed, they are listed in other_variants (check them: a short name like 'NextEra' is rarely the main variant). Sections:

  • queue: live renewable queue portfolio where a name is the developer, SPV or owner (your ISO permissions apply): totals (incl. the count where two sources agree on the developer), by ISO / fuel / state / developer label, live vs withdrawn, and the largest projects with links.
  • plants: operating renewable EIA-860 plants where a name is the EIA operator.
  • ppa: FERC EQR sales as seller (buyers, MWh, volume-weighted $/MWh) and purchases as buyer.
  • deals_news: curated deals naming the company plus EIA plant news (acquisitions, PPAs, funding first), each with a citation url.
  • entity: state business records, FERC registrations and parent companies verified from a public record.
  • sec: the SEC EDGAR registrant(s) a Load Factor analyst linked to these names (exact names only): CIK, tickers, industry, link class, latest fiscal-year financials, key metrics and peer percentiles, the renewable queue portfolio of its reviewed SEC-listed subsidiaries, subsidiary and filing counts, approved events and Form D raises. Reviewed rows only; an SEC-listed parent is the owner as of fiscal year-end, not the developer.

Returns {summary, names, match, scope, other_variants, one key per section, caveats}; each section has its own totals, lists and caveats. Plant parent/owner links are matched, not reviewed; queue MW in West, Southeast and CAISO is a bucket midpoint (mw_approximate). lists_shortened says which lists were cut.

match='contains' with name merges every variant containing the text, ignoring accents and lost d/s letters (broader, noisier). Request fewer sections to keep answers short; detail='detailed' returns longer lists.

Example

Ask your assistant:

It would call the tool with a request like this one (your client builds and sends it for you):

tools/call request
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_company_profile",
    "arguments": {
      "name": "Apex Clean Energy"
    }
  }
}

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.