HR-assist MCP server
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_employeeC | |
| get_employee_detailsB | |
| send_emailD | – |
| create_ticketC | |
| update_ticket_statusC | |
| list_ticketC | |
| schedule_meetingC | |
| get_meetingsA | |
| cancel_meetingsC | |
| get_employee_leavesC | |
| apply_leavesB | |
| get_leave_historyC | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| onboard_new_employee |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Tools cover distinct HR areas (employee info, tickets, meetings, leaves), with clear purposes. The only ambiguity is 'send_email', which lacks description and could overlap with notifications, but overall tools are distinct.
All tool names follow a consistent verb_noun pattern (e.g., add_employee, get_meetings, create_ticket). Minor singular/plural variations (e.g., get_meetings vs schedule_meeting) do not detract from overall coherence.
With 12 tools covering employee management, ticketing, meetings, and leave handling, the count is well-scoped for an HR assistant. No redundant or excessive tools.
The tool surface covers key workflows but has notable gaps: no employee update/delete, no ticket deletion, no meeting update, and no leave cancellation. These missing operations could cause agent failures in some scenarios.