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_employeeD | – |
| get_employee_detailsD | – |
| send_emailD | – |
| create_ticketD | – |
| schedule_meetingD | – |
| apply_leaveD | – |
| get_leave_historyD | – |
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 7 tools
Tool names map to fairly distinct actions (employee CRUD-ish, email, ticketing, meetings, leave), so an agent can mostly tell them apart. However, with no descriptions provided, boundaries like add_employee vs get_employee_details and the generic send_email/create_ticket/schedule_meeting are only inferable from names, leaving mild ambiguity.
All seven tools follow a clean snake_case verb_noun pattern (add_employee, get_employee_details, apply_leave, get_leave_history, etc.). No mixing of conventions or vague standalone verbs.
Seven tools is well-scoped for an HR assistant spanning employee records, leave, and administrative actions. Each tool appears to earn its place without redundancy.
The surface covers create/read for employees and full leave apply/history, but lacks update_employee, delete/offboard, or a list_employees operation, creating dead ends in the employee lifecycle. Generic email/ticket/meeting tools are present but no supporting read/list operations for them.