Skip to main content
Glama
ruchitha-meenakshi

HR-ASSIST

by ruchitha-meenakshi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CB_EMAILYesYour Gmail email address for sending emails.
CB_EMAIL_PWDYesYour Gmail app 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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_detailsC
Get employee details by name.
:param name: Name of the employee
:return: Employee ID and manager ID
send_emailC
Send an email to one or more recipients.
:param to_emails: List of email addresses
:param subject: Email subject
:param body: Email body content
:return: Success message
create_ticketC
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_ticketsC
List tickets for an employee with optional status filter.
:param employee_id: Employee ID
:param status: Ticket status (optional)
:return: List of tickets
schedule_meetingB
Schedule a meeting for an employee.
:param employee_id: Employee ID
:param meeting_datetime: Date and time in ISO format (YYYY-MM-DD HH:MM:SS)
:param topic: Topic of the meeting
:return: Confirmation message
get_meetingsC
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 in ISO format (YYYY-MM-DD HH:MM:SS)
:param topic: Topic of the meeting (optional)
:return: Confirmation message
get_employee_leave_balanceC
Get the leave balance of an employee.
:param emp_id: Employee ID
:return: Leave balance message
apply_leaveC
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_historyC
Get the leave history of an employee.
:param emp_id: Employee ID
:return: Leave history message

Prompts

Interactive templates invoked by user choice

NameDescription
onboard_new_employee

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 12 tools

Disambiguation4/5

Each tool has a distinct purpose, and there is no significant overlap between them. The only minor potential confusion is between 'get_employee_details' and 'get_employee_leave_balance' or 'get_leave_history', but these are clearly differentiated by their output focus.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., add_employee, get_employee_details, send_email), with no deviations. The naming is predictable and easy to understand.

Tool Count5/5

12 tools is a well-scoped number for an HR assistant, covering key operations without being overwhelming. Each tool appears to earn its place by addressing a specific need.

Completeness3/5

While core operations like employee management, ticketing, meetings, and leave are present, there are notable gaps: no update or delete for employees, no meeting update, and no way to list all employees or get details by ID. These missing operations could cause agent failures in common workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources