Skip to content
Load Factor Docs
Open Load Factor

MCP Tool

Fetch a Load Factor record

Fetch the full record for an id returned by search.

  • MCP
  • Read-only
  • Updated

Declaration

MCP tool
fetch(id: string)

Parameters

idstringRequired
Record id from search, e.g. project:J4196, company:Apex Clean Energy, company:cik:753308, plant:6002, news:<id>, deal:<id>, program:<id>, dg:<id>, article:<slug>.

Return Value

Returns {id, title, text, url, metadata}: text is a readable dossier (for a project: who is developing it and with what confidence, evidence summary, linked plant, PPA pricing, permits, news), url links to the record in the Load Factor app or the original source for citation.

Discussion

Fetch the full record for an id returned by search (or built by hand): project:<queue id>, company:<exact name>, company:cik:<SEC CIK> (a reviewed SEC registrant with the Load Factor profile of its linked names), plant:<EIA plant id>, news:<story id>, deal:<deal id>, insight:<id>, program:<DSIRE program id>, dg:<NY DG project id>, article:<slug> (a Load Factor Insights article: the whole article text).

Returns {id, title, text, url, metadata}: text is a readable dossier (for a project: who is developing it and with what confidence, evidence summary, linked plant, PPA pricing, permits, news), url links to the record in the Load Factor app or the original source for citation. On plans that open the full project dossier only for priority projects, other projects return their list-level fields (metadata.record = "list-level").

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": "fetch",
    "arguments": {
      "id": "project:J1229"
    }
  }
}

Availability

Listed to every account with MCP access. Results follow your Load Factor permissions (ISOs, detail level, evidence depth and rows per call). See Access & permissions.