> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nowadays.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Tools

> Every tool the Nowadays MCP server exposes, its arguments, and what it returns.

All five tools act as the signed-in user and work within one organization — the
one resolved automatically, or the one chosen with `select_organization`.

## `list_events`

Lists your organization's events, newest first.

| Argument | Type   | Description                             |
| -------- | ------ | --------------------------------------- |
| `page`   | number | 1-based page number (default `1`).      |
| `limit`  | number | Results per page, 1–100 (default `20`). |

Returns each event's `id`, `name`, `dates`, `locations`, `numPeople`, `status`
and `createdAt`, plus `page`, `limit` and `total`.

## `get_event`

Gets a single event's detail by its `id`.

| Argument   | Type   | Description                                                 |
| ---------- | ------ | ----------------------------------------------------------- |
| `event_id` | string | The event's public id (UUID), as returned by `list_events`. |

Returns the `list_events` fields plus `venueType`, `numHotelRoomsNeeded`,
`isMultiDay`, `otherNotes` and `currency`.

An id that does not exist, and one belonging to another organization, both return
the same not-found error — you never learn whether another organization's event
exists.

## `create_event`

Creates a new event in your organization. You become its owner.

| Argument                   | Type   | Description                                                                                     |
| -------------------------- | ------ | ----------------------------------------------------------------------------------------------- |
| `name`                     | string | Event title. Required.                                                                          |
| `formattedLocations`       | array  | Candidate cities, e.g. `[{ "city": "Austin" }]`.                                                |
| `eventDates`               | array  | Inclusive `YYYY-MM-DD` ranges, e.g. `[{ "startDate": "2027-03-15", "endDate": "2027-03-17" }]`. |
| `venueType`                | string | Defaults to `hotel`.                                                                            |
| `numPeople`                | number | Total attendees.                                                                                |
| `numHotelRoomsNeeded`      | number | Guestrooms needed.                                                                              |
| `meetingRooms`             | string | Free-text meeting-room requirement.                                                             |
| `foodBeverageRequirements` | string | Free-text F\&B needs.                                                                           |
| `currency`                 | string | Defaults to `USD`.                                                                              |

Returns the new event's `id` and `grantedTo` — how many people can now see it.

<Warning>
  A `grantedTo` of `0` means the event was created but is **not yet visible to
  anyone** — see [Writing events](/mcp/writing-events) for why and what to do.
</Warning>

## `update_event`

Changes an event's planning details — dates, headcount, budget, guestrooms,
agenda and notes.

| Argument   | Type   | Description                   |
| ---------- | ------ | ----------------------------- |
| `event_id` | string | The event's public id (UUID). |
| `changes`  | object | Only the fields to change.    |

```json theme={null}
{
  "event_id": "3f2b…",
  "changes": {
    "numPeople": 320,
    "agendaOperations": [
      { "op": "update", "sessionId": "a1b2…", "session": { "startTime": "09:30" } }
    ]
  }
}
```

Call `get_event` first so you are editing current values. The write rules —
omitted-versus-null, all-or-nothing, agenda-by-operation, and the two refusals
you can hit — are covered in [Writing events](/mcp/writing-events).

## `select_organization`

Only needed if your account belongs to **more than one** organization. Call it
once to choose which organization the event tools work in; the choice is
remembered for this client until you change it.

| Argument         | Type   | Description                                                                             |
| ---------------- | ------ | --------------------------------------------------------------------------------------- |
| `organizationId` | string | The id of the organization to use (offered by `list_events` when a choice is required). |

If you belong to a single organization, this tool is unnecessary — the other
tools resolve it automatically.