Skip to main content
Glama
lalithdabilpuram01

HRMS MCP Server

by lalithdabilpuram01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MS_EMAILYesSender email address / SMTP login
MS_EMAIL_PWDYesSMTP password or 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_detailsA
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_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 : status
: return : List of tickets

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

C2.8/5.0

Scored across 6 tools

Disambiguation4/5

Most tools have clear, distinct purposes (employee CRUD, ticket management). However, 'send_email' lacks a description, making its role ambiguous and potentially overlapping with ticket notifications.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., add_employee, create_ticket, list_tickets). No mixing of conventions.

Tool Count5/5

6 tools is a reasonable count for an HRMS server covering employee and ticket management. Not too few or too many.

Completeness3/5

Missing employee update/delete and ticket detail retrieval. Employee lookup only by name, not ID. Notable gaps in CRUD coverage for both domains.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources