Skip to main content
Glama
Sign In
hr-assist

hr-assist

by paras2026-git
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CB_EMAILYesYour email address used for sending emails over SMTP
CB_EMAIL_PWDYesYour Gmail App Password (not your normal password) used for sending emails over SMTP

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_employeeA
Add a new employee to the HRMS system.
:param emp_name: Full name of the new employee
:param email: Email address of the new employee
:param manager_id: Employee ID of the manager, e.g. "E003" (optional; use get_employee_details to find it)
:return: Confirmation message that includes the new employee ID
get_employee_detailsA
Get employee details by employee ID (e.g. "E003") or by name (full or partial).
:param name: Employee ID or name of the employee
:return: emp_id, name, manager_id (None if the employee has no manager) and email
send_emailB
Send an email.
:param to_emails: List of recipient email addresses
:param subject: Subject line
:param body: Email text
:param html: True if the body is HTML
:return: Confirmation 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_ticketsA
List tickets, optionally filtered by employee and/or status.
:param employee_id: Employee ID (optional)
:param status: Ticket status: Open, In Progress, Closed or Rejected (optional)
:return: List of tickets
schedule_meetingC
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_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 of the meeting in python datetime format
: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 in YYYY-MM-DD format
: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

Disambiguation5/5

Each tool targets a distinct HR resource and action: employees, tickets, meetings, leave, or email. There is no meaningful overlap that would cause an agent to select the wrong tool.

Naming Consistency4/5

All tools use snake_case with a verb_noun pattern, which is predictable overall. Minor inconsistencies appear in noun forms such as schedule_meeting vs get_meetings and get_employee_details.

Tool Count5/5

With 12 tools, the set is well within a reasonable range for an HR assistant. Each tool corresponds to a clear operational need across employees, tickets, meetings, leave, and email.

Completeness3/5

Core workflows are present, but notable lifecycle gaps remain: employees can be added and fetched but not updated, deleted, or listed; tickets can be listed and status-updated but not fetched individually; leave cannot be cancelled or approved. These gaps are workable but will limit some common HR operations.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues

Resources