# Queue statistics (`queue_stats`)

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

Counts and capacity of renewable queue projects grouped by one dimension (iso, fuel, state, county, status, confidence, developer, queue_year, in_service_year, study_cycle, project_stage), optionally pivoted by a second one. Each group returns projects, total MW, average MW, the count where two sources agree on the developer (`confirmed_developer`) and the share with any developer named; overall totals are computed over every matching project.

Takes the same filters as search_projects. Default status='live' = not withdrawn, INCLUDING operating plants (totals report how many are operating); use status='in_queue' for the not-yet-built pipeline, status='operating' for built plants, or status='all' (with group_by=status) to see the status mix. PJM duplicate rows are excluded unless include_duplicates=true. study_cycle is only populated for MISO.

Returns {summary, group_by, second_group_by, totals, groups_total, groups, filters, caveats}. Each `groups` row has `group` (and `subgroup` when pivoted), `projects`, `mw`, `avg_mw`, `confirmed_developer` and `pct_with_developer`; a missing value reads '(not reported)'. `groups_total` counts every group even when `limit` shows fewer. MW in West, Southeast and CAISO is approximate (bucketed) and PJM MW is capacity (CIR) MW; `caveats` says which apply.

Use this for "how many / how much MW" questions; use search_projects to list the projects themselves.

## Parameters

| Parameter | Type | Required | Description | Allowed values | Default |
|---|---|---|---|---|---|
| `group_by` | string | yes | Dimension to group by. county groups are 'County, ST'; queue_year / in_service_year come from the queue dates; developer excludes projects with no developer; confidence groups by the web app's badge (confirmed = two sources agree, developer_of_record = named in the queue, inferred, unknown = not identified). | iso, fuel, state, county, status, confidence, developer, queue_year, in_service_year, study_cycle, project_stage |  |
| `second_group_by` | string | no | Optional second dimension for a pivot (e.g. group_by=iso, second_group_by=fuel). | iso, fuel, state, county, status, confidence, developer, queue_year, in_service_year, study_cycle, project_stage |  |
| `iso` | string | no | ISO/region, or comma-separated list: PJM, MISO, ERCOT, SPP, CAISO, NYISO, ISO-NE, West, Southeast, IESO, AESO, Maritimes, Quebec, BC, Saskatchewan, Manitoba. |  |  |
| `state` | string | no | Two-letter state/province code(s), comma-separated, e.g. 'TX' or 'IL,IN'. |  |  |
| `fuel` | string | no | Fuel(s), comma-separated: Solar, Wind, Offshore Wind, Battery Storage, Hybrid, Hydro, Biomass, Biogas, Biofuel, Wood, Geothermal. |  |  |
| `status` | string | no | Queue status filter. live (default) = not withdrawn/suspended, INCLUDING projects already operating/in service; in_queue = not withdrawn and not yet operating (the development pipeline); operating = in service; withdrawn = withdrawn/suspended/cancelled; all = everything. | in_queue, live, withdrawn, operating, all | live |
| `confidence` | string | no | confirmed = two sources agree: two or more independent strong records name the developer; developer_of_record = named in the queue: the grid operator's queue names it and nothing else strong does yet; any_developer = a developer is named at any confidence; unknown = not identified: no developer identified; all (default). | confirmed, developer_of_record, any_developer, unknown, all | all |
| `developer` | string | no | Developer / SPV / owner name (substring). Use find_companies first to see name variants. |  |  |
| `min_mw` | number | no | Minimum summer MW. |  |  |
| `max_mw` | number | no | Maximum summer MW. |  |  |
| `include_duplicates` | boolean | no | Include PJM duplicate rows (the older '<id>' row whose queue position moved to '<id> - moved to TC1/TC2', and '<id> <number>' copies of '<id>-<number>'). Default false so counts and MW are not double-counted. |  | false |
| `sort` | string | no | Group order: auto (default) = chronological for year groupings, else most projects; projects; mw; group = alphabetical. | auto, projects, mw, group | auto |
| `limit` | integer | no | Groups (rows) to return, max 100. |  | 25 |

## Example

Ask your assistant: "Rank the top 10 developers of solar projects in the MISO queue."

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": "queue_stats",
    "arguments": {
      "group_by": "developer",
      "iso": "MISO",
      "fuel": "Solar",
      "limit": 10
    }
  }
}
```

## 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).
