Tool reference · Team onboarding
New in 14.6.0onboarding_team_report
Department report: every member against every module with status, lessons done, quiz results and dates, the learning log, and (for heads) the grading queue.
team server /mcp
Caution. Requires the department head role for that team, company_viewer or superadmin.
When to use
- A department head types /onboard-report.
- A company viewer checks how a department's new hires are doing.
- You need the grading queue before calling onboarding_grade.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
team_idrequired | string | — | (pattern ^[a-zA-Z0-9_-]{1,64}$) |
Example
Arguments
{
"team_id": "eng"
} Result shape
{
"team_id": "eng",
"title": "Engineering onboarding",
"generated_at": "2026-09-25T10:05:00.000Z",
"modules": [
{
"module_id": "mod_deploy",
"title": "Deploy"
}
],
"members": [
{
"user_id": "petr",
"name": "Petr Backend",
"role": "editor",
"enrolled_at": "2026-09-25T09:40:11.020Z",
"summary": {
"lessons_completed": 2,
"lessons_total": 4,
"modules_finished": 1,
"modules_total": 2,
"percent": 50,
"updated_lessons": 0
},
"modules": [
{
"module_id": "mod_deploy",
"title": "Deploy",
"status": "pending_review",
"lessons_completed": 2,
"lessons_total": 2,
"started_at": "2026-09-25T09:40:30.000Z",
"lessons_finished_at": "2026-09-25T09:55:02.000Z",
"quiz": {
"attempts_used": 1,
"attempts_left": 2
}
}
]
}
],
"log": [
{
"at": "2026-09-25T09:58:13.000Z",
"event": "quiz_submitted",
"summary": "Petr Backend took the quiz of module 'Deploy' on 2026-09-25: 1/3 (33%) so far, open answers await review"
}
],
"grading_queue": [
{
"attempt_id": 17,
"question_id": "q_billing",
"user_id": "petr",
"module_id": "mod_deploy",
"submitted_at": "2026-09-25T09:58:13.000Z",
"prompt": "Why do billing changes need two approvals?",
"rubric": "Billing is high-risk; a second reviewer catches mistakes.",
"points": 2,
"answer": "Because billing is sensitive."
}
]
} grading_queue is included only for people who can grade (the department head and superadmins).
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 report for heads, company viewers and superadmins: every member x module with status, quiz scores and dates, recent learning log and (for heads) the open-answer grading queue.