# People and organisations

## Where to start: `list_organisations` and `list_projects`

Most tools need an id. These two provide it, without a detour through the app.

`list_organisations` has no arguments. Each row names id, name, subdomain and `scope`:
`all_projects`, or `selected_projects` for a token that reaches only some projects.

`list_projects` names the projects the token reaches and you may read.

| Argument | Meaning |
|---|---|
| `organisation_id` | this organisation only |
| `include_archived` | archived projects too |
| `page`, `per_page` | page, at most 100 per page |

Only an account admin sees archived projects.

## Search people: `find_people`

Searches an organisation's [people directory](https://lalabase.com/docs/en/guides/people/directory): members with a
login and contacts without one, such as at customers or suppliers.

| Argument | Meaning |
|---|---|
| `organisation_id` | required, the organisation |
| `query` | one short word stem, such as `techn` or a company name |
| `kind` | `all` (default), `members` or `contacts` |

The search covers name, function, department, company, email and additional details, ignoring
case. The answer holds at most 20 people. If it says `truncated`, a longer stem helps.

## Read one person: `get_person`

Takes `organisation_id` and the `id` from `find_people`, so `person:<uuid>` or `member:<uuid>`, and
returns contact details such as email and phone.

## Limits

- Only a token that reaches **all projects** of the organisation reads the directory. To a token
  limited to some projects, the organisation counts as not found here.
- Notes about a person never come over MCP.
- What you may see in the directory yourself applies.