Tool reference · Team onboarding
New in 14.6.0onboarding_curriculum_set
Creates or replaces a department's curriculum: ordered modules of ordered lessons with text and/or team memory record IDs.
team server /mcp
Caution. A stale expected_revision is rejected with a conflict. Record IDs must exist in team memory. Keep existing module and lesson ids so employees keep their progress; omitted items are archived.
When to use
- Publishing a reviewed draft from onboarding_curriculum_draft.
- Adding, reordering or retiring modules and lessons.
- Changing a module's pass threshold or attempt limit.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
team_idrequired | string | — | (pattern ^[a-zA-Z0-9_-]{1,64}$) |
expected_revisionrequired | integer | — | Revision from onboarding_curriculum_get; 0 when creating. (min 0) |
curriculumrequired | { title, modules } | — | — |
Example
Arguments
{
"team_id": "eng",
"expected_revision": 3,
"curriculum": {
"title": "Engineering onboarding",
"modules": [
{
"id": "mod_deploy",
"title": "Deploy",
"pass_threshold": 0.8,
"max_attempts": 3,
"lessons": [
{
"id": "les_pipeline",
"title": "Pipeline",
"body": "How a change reaches production.",
"record_ids": [
42
]
}
]
}
]
}
}Result shape
{
"team_id": "eng",
"revision": 4,
"updated_by": "boss",
"curriculum": {
"title": "Engineering onboarding",
"modules": []
}
}Returns the saved curriculum in the same shape as onboarding_curriculum_get.
Values are illustrative; the keys follow the server's handler. MCP clients receive the result as JSON text content.
Server description
The description the server sends to your agent in tools/list, captured from the v14.7.0 source:
Department head: create or replace the curriculum (ordered modules -> lessons with text and/or team record IDs). Keep existing ids to preserve progress; omitted items are archived.