onboarding
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| onboarding_hire_addA | Add a new hire and return its H-NNNN id: a name, a role and the day they start. The role is a grouping key, lower-cased and hyphenated. Add tasks with onboarding_task_add, or apply a role template with onboarding_template_apply. |
| onboarding_hire_listA | Every hire with their role, start date, task counts, percent complete and overdue count. Filter by role or by a word in the name. Returns at most 500 rows, newest change first. |
| onboarding_task_addA | Add one task to a hire's plan and return its K01-style id: the text, who owns it (hr, manager or it) and how many days after the start date it is due. The due date is counted from the hire's start date. |
| onboarding_task_doneA | Mark one task on a hire done or skipped, with the day it happened. done counts toward the percent complete; skipped is a deliberate dismissal and never counts as done. A task can be set back to todo to reopen it. |
| onboarding_template_applyA | Apply a role template to one hire (free) or many (Pro), copying the template's tasks into each hire with the template's version recorded. Editing the template afterwards never changes a hire already under way. If no template exists for the role, one is created from the tasks you pass. |
| onboarding_progressA | One hire's whole plan: every task with its owner, due date and status, plus the percent complete, the overdue count and what is still outstanding. Pass as_csv for a Pro-only CSV export of the plan. |
| onboarding_overdueA | Every task that is still outstanding past its due date, across all hires or one hire, with how many days late. Returns at most 500 rows, most overdue first. |
| license_statusA | Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key. |
| license_activateA | Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| onboard_a_hire | Add the hire, build or apply a role template, mark tasks done as they happen, and watch progress and overdue. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| contract | Why a hire copies its template, the three task states and what skipped means, the free-tier limits and the one file this server writes. |
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action: hires, tasks, templates, progress, overdue, and licensing are clearly separated. Even the overlapping summary tools (hire_list vs progress vs overdue) are differentiated by aggregate list vs single-plan detail.
Most tools follow a consistent snake_case pattern with domain prefixes like onboarding_ and license_, and a resource-action structure such as hire_add, task_done, template_apply. The exceptions are onboarding_progress and onboarding_overdue, which use noun/adjective commands rather than an explicit verb, and license_status which is noun-like.
Nine tools is a well-scoped set for an onboarding workflow: hire creation, task management, template application, progress/overdue reporting, and license handling. Each tool has a clear purpose and none feel redundant or bloat the surface.
Core workflows are covered: add hires, add/complete tasks, apply templates, view progress, and check overdue items. However, there are notable lifecycle gaps: no way to update or delete a hire, no task edit/removal, and no template management beyond applying one.