MCP Workforce Guardian
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_workerA | Look up a single worker by id. Safe, read-only, never requires approval. |
| search_workersA | Search workers by name substring (case-insensitive). Safe, read-only. |
| get_daily_planA | Get today's production plan: which lines/cells need how many workers. |
| list_open_cellsA | List production cells that are currently short-staffed today. |
| mark_attendanceA | Mark whether a worker is present today. Routine, not gated. |
| allocate_workerB | Assign a worker to a production line/cell. Routine, not gated. |
| update_workerA | Update a worker's editable fields: skill_level, employment_status, notes, age. Changes to employment_status require human approval. Output and rejected-part counts are not editable here; use log_hourly_output. |
| log_hourly_outputA | Record this hour's output for a worker. If the reported count is far from the worker's normal rate, the write requires human approval first. |
| terminate_workerB | Terminate a worker's employment. Always requires human approval. |
| delete_workerB | Permanently delete a worker's record. Always requires human approval. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools target distinct resources and actions, such as get_worker vs search_workers and mark_attendance vs log_hourly_output. However, get_daily_plan and list_open_cells overlap somewhat in that both surface staffing needs, which could cause minor confusion.
All tools follow a clear verb_noun pattern: get_worker, search_workers, delete_worker, allocate_worker, log_hourly_output. Even retrieval verbs (get vs list) are used consistently for plan vs cell views, keeping the set predictable.
Ten tools cover worker lookup, management, planning, attendance, allocation, and output logging without feeling bloated. Each tool addresses a distinct operational need for a workforce management server, so the count is well-scoped.
The tool set covers lookup, search, update, delete, attendance, allocation, planning, and output logging, but there is no create_worker or onboarding tool. This is a notable gap in worker record lifecycle management, though existing workers can be managed effectively.