Skip to main content
Glama
Ayush-og

atliq-hrms-assist

by Ayush-og
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CB_EMAILYesYour Gmail address used for sending emails.
CB_EMAIL_PWDYesYour Gmail app password, not your regular Gmail 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.

get_employee_detailsB

Get employee details by name.

get_leave_balanceA

Get the current leave balance for an employee.

apply_leaveA
Apply for leave on specified dates.
:param employee_id: Employee ID (e.g. 'E004')
:param leave_dates: List of dates in YYYY-MM-DD format (e.g. ['2026-08-15', '2026-08-16'])
:return: Confirmation message with remaining balance
get_leave_historyA

Retrieve past leave history for an employee.

schedule_meetingA
Schedule a meeting for an employee.
:param emp_id: Employee ID (e.g. 'E004')
:param meeting_dt: Scheduled Date and Time in ISO format (e.g. '2026-08-15T10:00:00')
:param topic: Meeting subject or topic
:return: Confirmation string
get_meetingsC

Get all scheduled meetings for an employee.

cancel_meetingB

Cancel a scheduled meeting for an employee.

create_ticketA
Create a support or equipment request ticket for an employee (e.g., Laptop, ID Card).
:param emp_id: Employee ID (e.g. 'E004')
:param item: Name of the requested item or equipment
:param reason: Reason for the request
:return: Confirmation string with ticket ID
update_ticket_statusA

Update the status of a ticket (Open, In Progress, Closed, Rejected).

send_emailB

Send an email to one or more recipients.

Prompts

Interactive templates invoked by user choice

NameDescription
onboard_new_employee
apply_leave_request
schedule_meeting_request

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

A3.6/5.0

Scored across 11 tools

Disambiguation5/5

Each tool targets a distinct resource (employee, leave, meeting, ticket, email) with a clear action. There is no overlap in functionality, even though employee identifiers vary between tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (add_, get_, apply_, schedule_, cancel_, create_, update_, send_). This uniformity makes the API predictable.

Tool Count5/5

At 11 tools, the server covers multiple HR subdomains without unnecessary bloat. The count is well within the ideal range for a focused assistant.

Completeness3/5

The server covers core workflows for employees, leave, meetings, tickets, and email. However, employee update/delete and leave cancellation are missing, creating notable lifecycle gaps. Ticket viewing is also absent, though the creation and status update flow works.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources