Skip to main content
Glama
sachink1712

HR Assistant MCP Agent

by sachink1712
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CB_EMAILYesYour Gmail email address used for sending transactional emails.
CB_EMAIL_PWDYesYour Gmail app password (not your regular account 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_employeeB
Add a new employee to the system.
Args:
    name: str
    manager_id: str
    email: str
Returns:
    str
get_employee_detailsC
Get the details of an employee by name.
Args:
    name: str
Returns:
    Dict[str, Any]
send_emailC
Send an email to an employee.
Args:
    to_email: str
    subject: str
    body: str
Returns:
    str
create_ticketB
Create a ticket for an new employees to get a new laptop, id card, and other necessary equipment.
Args:
    emp_id: str
    item: str
    reason: str
Returns:
    str
schedule_meetingC
Schedule a meeting for an employee.
Args:
    emp_id: str
    meeting_dt: datetime
    topic: str
Returns:
    str
get_leave_balanceC
Get the leave balance of an employee.
Args:
    emp_id: str
Returns:
    str
apply_leaveB
Apply leave for an employee.
Args:
    emp_id: str
    leave_dates: List[datetime]
Returns:
    str
get_leave_historyB
Get the leave history of an employee.
Args:
    emp_id: str
Returns:
    str

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 8 tools

Disambiguation5/5

Each tool maps to a distinct HR function: employee creation/retrieval, email, IT ticket, meeting scheduling, and leave operations. The leave tools are clearly separated into balance, application, and history, so there is little risk of an agent selecting the wrong one.

Naming Consistency4/5

Tool names mostly follow a consistent verb_noun snake_case pattern such as add_employee, get_leave_balance, and schedule_meeting. Minor inconsistency exists between add_employee and create_ticket, but the overall convention is predictable and readable.

Tool Count5/5

Eight tools is a well-scoped size for an HR assistant covering employee records, leave, meetings, email, and onboarding tickets. Each tool represents a meaningful workflow area without unnecessary overlap or bloat.

Completeness3/5

The set covers core employee and leave operations, but obvious gaps remain: there is no update or delete employee, no list employees, and no leave cancellation or approval workflow. These gaps are workable for basic scenarios but could cause failures in fuller HR processes.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources