AtliQ HR Assist
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 | Add a new employee to the HRMS system. :param emp_name: Employee name :param manager_id: Manager ID (optional) :return: Confirmation message |
| get_employee_detailsA | Get employee details by name : param name: Employee name :return: Employee id and manager id |
| update_employeeD | – |
| delete_employeeD | – |
| get_leave_balanceA | Get current leave balance of an employee. Args: employee_id: Employee ID (e.g. E004) Returns: Current leave balance. |
| get_leave_historyD | – |
| send_emailD | – |
| create_ticketD | – |
| schedule_intro_meetingD | – |
| apply_leaveC | Apply leave for an employee. Example: leave_dates = ["2026-07-20", "2026-07-21"] |
| update_leave_balanceD | – |
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 11 tools
Many tools lack descriptions, making it hard to distinguish them. 'apply_leave' and 'get_leave_history' could be confused, and 'create_ticket' is ambiguous as it doesn't fit the HR domain clearly.
Tools mostly follow a verb_noun pattern but the verbs are inconsistent (add, apply, create, delete, get, schedule, send, update). Some tools like 'get_employee_details' and 'get_leave_balance' align, but overall lacks a uniform convention.
With 11 tools, the count is reasonable for an HR system. However, tools like 'create_ticket' and 'send_email' might be extraneous, slightly increasing the scope beyond core HR.
Missing descriptions for several tools hinder assessment. Obvious gaps exist: no tool for listing employees, no leave approval workflow, and no role management. The surface feels incomplete for a typical HR system.