# My Load Factor access (`whoami`)

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

Show the signed-in user's Load Factor access as this connector enforces it: email, role, the ISOs/regions they can query (or ALL), per-ISO permission levels (full or restricted view, full or summary evidence, whether proof explanations are shown, export, rows per call), enabled modules, and which tool groups this connection can call.

Returns {summary, email, name, role, is_admin, connection, isos, permissions, modules, rows_per_call, tool_groups, resources, prompts, what_this_means}: `permissions` has one row per ISO (`view`, `evidence`, `proof`, `export`, `max_rows`), each `tool_groups` entry lists its callable `tools` or what it `requires`, and `what_this_means` spells out the restrictions in plain words.

Use it when a result looks filtered or empty, when an expected tool is missing, or when the user asks what they can see. Restricted view hides coordinates, SPV/interconnection-customer and owner names and source URLs, and limits project detail to priority projects; summary evidence hides source URLs and raw source text. For what data exists, how many rows and how fresh it is, use data_catalog.

## Parameters

This tool takes no parameters.

## Example

Ask your assistant: "What can I access through Load Factor?"

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": "whoami",
    "arguments": {}
  }
}
```

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