HR-ASSIST
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CB_EMAIL | Yes | Your email address | |
| CB_EMAIL_PWD | Yes | Your email provider's app-specific password |
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_statusA | Update the status of a ticket. :param ticket_id: Ticket ID :param status: New status (Open, In Progress, Closed) |
| list_ticketsB | List tickets for an employee with optional status filter. :param employee_id: Employee ID (optional) :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_all_meetings_for_employeeB | Get the list of meetings scheduled for an employee. :param employee_id: Employee ID :return: List of meetings |
| cancel_meetingA | 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_historyA | Get the leave history of an employee. Args: emp_id (str): the employee ID for whom the leave history is being requested Returns: List[Dict[str, str]]: List of leave history entries |
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
Each tool targets a distinct resource/action: employee management, email, tickets, meetings, and leave. No two tools overlap in purpose, making selection unambiguous.
All tools follow a consistent verb_noun pattern in snake_case (add_employee, get_employee_details, create_ticket, schedule_meeting, etc.). No mixed conventions or chaotic naming.
With 12 tools covering multiple HR sub-domains (employee, ticket, meeting, leave, email), the count is well-scoped and appropriate for the server's purpose, neither too thin nor overwhelming.
Core workflows are covered: employee creation/retrieval, ticket lifecycle (create/update/list), meeting scheduling/cancellation/list, leave balance/apply/history. Minor gaps exist (e.g., no employee update/delete, no single ticket detail, no leave cancellation) but they are workable.