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

# Workout of the Day

> Company MCP reference for WOD schedules, publishing, settings, and verified leaderboards.

The `wod` company module manages scheduled Workouts of the Day and exposes
verified leaderboard results. Runtime authorization applies WOD feature,
company-role, RBAC permission, publication, and settings checks for each action.

| Key                     | Value                                               |
| :---------------------- | :-------------------------------------------------- |
| **Module key**          | `wod`                                               |
| **Sensitivity**         | `health`                                            |
| **Consent required**    | `healthDataConsent`                                 |
| **Feature requirement** | WOD enabled for operational WOD reads and mutations |

## Read tools

### `get_wod_settings`

Returns WOD feature, visibility, notification, publication, approval, and score
verification settings without creating or changing a settings record.

### `list_wods`

Lists company WODs. Optional fields are `status` (`draft`, `published`, or
`archived`), `dateFrom`, `dateTo`, `page`, and `limit`. Dates use `YYYY-MM-DD`,
the range cannot exceed 366 days, and the page limit is 50.

### `get_wod`

Returns one company-scoped WOD and its bounded workout prescription. Requires
`wodId`.

### `get_wod_by_date`

Returns the published WOD for one canonical date. The `date` argument
(`YYYY-MM-DD`) is optional and defaults to today in the connected company's
configured timezone, so calling this tool without arguments returns today's
WOD.

### `get_wod_leaderboard`

Returns a bounded page of verified leaderboard results. Requires `wodId`;
`page` and `limit` are optional, with a maximum limit of 50.

## Write tools

All write tools require explicit grant approval and
`params._meta.idempotencyKey`. See [Connection & Protocol](/mcp/connection) for
the durable replay contract. Publish and archive permissions are separate from
create and update permissions.

### `create_wod` **`Write`**

Creates a draft WOD from an existing company workout template and plan moment.
Requires `planId`, `planMomentId`, and `scheduledDate`. Optional fields include
localized title and description, scoring, target, divisions, and score
validation. Publishing requires a separate `publish_wod` call.

### `create_custom_wod` **`Write`**

Creates a custom draft WOD and backing workout plan after validating every
exercise. Requires `scheduledDate`, localized `title`, and one to 50 `exercises`;
localized description, scoring type, and target are optional.

### `update_wod` **`Write`**

Updates WOD content without changing publication state. Requires `wodId`;
template references, schedule, localized content, scoring, divisions, score
validation, and exercises are optional updates.

### `publish_wod` **`Write`**

Publishes a draft or archived WOD when coach access, company settings, and WOD
publish permission allow it. Requires `wodId`.

### `archive_wod` **`Write`**

Removes a WOD from active publication while retaining it for later republishing.
Requires `wodId` and is marked destructive in its MCP annotations.

## Natural Language Examples

* *"What's the WOD for today?"*
* *"Create a draft WOD for next Monday with a 20-minute AMRAP."*
* *"Show me the leaderboard for yesterday's WOD."*
* *"Publish the draft WOD for tomorrow."*

## JSON-RPC Call Example

```json theme={null}
{
  "jsonrpc": "2.0",
  "id": "wod-1",
  "method": "tools/call",
  "params": {
    "name": "get_wod_by_date",
    "arguments": {
      "date": "2026-08-10"
    }
  }
}
```