# List project evidence (`get_project_evidence`)

A read-only tool of the Load Factor MCP server (https://mcp.loadfactorenergy.com/mcp), in the Queue projects group.

List the active evidence rows behind one queue project's developer identification, from grid-operator queues, federal filings, corporate disclosures, state and local public records, plant data and news.

Each row has `source` (the source as the Load Factor web app names it, e.g. "Interconnection agreement" or "ISO queue (official)"), `source_family` (grid-operator filings, federal regulatory filings, corporate disclosures, state and local public records, plant and market data, news and announcements, other public records, analyst review), `strength` (Strong, Supporting or Lead, the words the web app shows), extracted_role and extracted_name, document title/date, and `supports` when the row backs the resolved developer, interconnection customer or owner. Rows are ordered strongest first, then most recent. The response includes the total matching count and counts by source (`by_source`) and by family (`by_family`), so you can narrow with source, family, role or min_strength and page with offset.

Returns {summary, project_number, iso, url, total, offset, next_offset, filters, by_source, by_family, results, caveats}, plus `sec_parent` when one is on record. `results` is one page of evidence rows; continue with `offset` = `next_offset` (null on the last page). County records still awaiting review carry `status: pending_review`. A capped page carries `truncated` and a `truncation_note`.

Use get_project first for the overall answer; use this for the underlying records and citations. Personal details such as landowner names and addresses are never returned. A parent_owner row names the owner as of fiscal year-end, not the developer, and the response adds the reviewed `sec_parent`; rows from before the review process are legacy and unreviewed and read "SEC EDGAR (unreviewed)".

## Parameters

| Parameter | Type | Required | Description | Allowed values | Default |
|---|---|---|---|---|---|
| `project_number` | string | yes | Queue ID exactly as search_projects returns it (or the typed id from `search`, project:J4196). |  |  |
| `iso` | string | no | Optional ISO hint when the same ID exists in two ISOs. |  |  |
| `source` | string | no | Only rows from this source, exactly as listed in by_source in a previous response for the same project (e.g. "Interconnection agreement", "ISO queue (official)"); case-insensitive. |  |  |
| `family` | string | no | Only rows from this source family, as listed in by_family: grid-operator filings, federal regulatory filings, corporate disclosures, state and local public records, plant and market data, news and announcements, other public records, analyst review. A distinctive word works too (e.g. "federal"). |  |  |
| `role` | string | no | extracted_role, e.g. developer, interconnection_customer, project_owner, project_name, operator, ppa_buyer, land_control_party, parent_owner. |  |  |
| `min_strength` | string | no | Only rows at this strength or stronger, in the web app's words: strong (official records that name the company directly), supporting (strong and supporting rows), lead or any (default: every row). | strong, supporting, lead, any |  |
| `source_type` | string | no | Deprecated: use `source`. Still accepted for older clients. |  |  |
| `max_tier` | integer | no | Deprecated: use `min_strength`. Still accepted for older clients. |  |  |
| `limit` | integer | no | Rows to return (max 50). |  | 20 |
| `offset` | integer | no | Skip this many rows (paging). |  | 0 |

## Example

Ask your assistant: "Show the evidence behind the developer attribution for project J1229."

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_project_evidence",
    "arguments": {
      "project_number": "J1229",
      "limit": 20
    }
  }
}
```

## 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](https://loadfactorenergy.com/developers/mcp/access-and-permissions).
