hr-assist
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CB_EMAIL | Yes | Your email address used by HR Assist | |
| CB_EMAIL_PWD | Yes | Your email provider's app-specific password (e.g., for Gmail) |
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 | Add a new employee to the HRMS system. :param emp_name: Employee name :param manager_id: Manager ID (optional) :return: Confirmation message |
| get_employee_detailsB | Get employee details by name. :param name: Name of the employee :return: Employee ID and manager ID |
| send_emailD | – |
| create_ticketA | Create a ticket for buying required items for an employee. :param emp_id: Employee ID :param item: Item requested (Laptop, ID Card, etc.) :param reason: Reason for the request :return: Confirmation message |
| update_ticket_statusB | Update the status of a ticket. :param ticket_id: Ticket ID :param status: New status of the ticket :return: Confirmation message |
| list_ticketsA | List tickets for an employee with optional status filter. :param employee_id: Employee ID :param status: Ticket status (optional) :return: List of tickets |
| schedule_meetingA | Schedule a meeting for an employee. :param employee_id: Employee ID :param meeting_datetime: Date and time of the meeting in python datetime format :param topic: Topic of the meeting :return: Confirmation message |
| get_meetingsB | Get the list of meetings scheduled for an employee. :param employee_id: Employee ID :return: List of meetings |
| cancel_meetingC | Cancel a scheduled meeting for an employee. :param employee_id: Employee ID :param meeting_datetime: Date and time of the meeting in python datetime format :param topic: Topic of the meeting (optional) :return: Confirmation message |
| get_employee_leave_balanceB | Get the leave balance of an employee. :param emp_id: Employee ID :return: Leave balance message |
| apply_leaveA | Apply for leave for an employee. :param emp_id: Employee ID :param leave_dates: List of leave dates :return: Leave application status message |
| get_leave_historyB | Get the leave history of an employee. :param emp_id: Employee ID :return: Leave history message |
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 have distinct purposes related to employee management, leave, tickets, and meetings. However, 'send_email' has no description, creating ambiguity about its scope and potential overlap with other communication tools.
Most tool names follow a consistent verb-noun pattern (e.g., get_leave_history, add_employee, update_ticket_status). Minor deviations like 'send_email' and 'schedule_meeting' still fit the pattern, but the mix of 'emp_id' and 'employee_id' in parameters is slightly inconsistent.
12 tools is well-scoped for an HR assistant, covering employee records, leave, tickets, and meetings without redundancy. Each tool appears to serve a distinct function.
Core operations for leave and tickets are present, but missing update/delete for employee records and leave, and the 'send_email' tool lacks description, suggesting an incomplete or unclear communication surface.