Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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 new employee to the hrms system
:param emp_name :takes new employee name
:param manager_id :takes the manager id
returns: Confirmation message
get_employee_detailsB
Get the employee details by name
:param name: Name of the employee
returns employee ID or Manager ID
send_emailD–
create_ticketC
Create ticket for buying items for the employee
:param emp_name: Nane of the employee
:param item: Item Requested(example: Laptop or ID)
:param reason: reason for the request
returns : Confiramtion of Ticket Genrated
update_ticket_statusC
Update the status of the ticket
:param emp_id: Id od the employee
:status : Status od the ticket
returns : Confirmation message 
list_ticketC
Get the list of the tickets
:param emp_id: Id of employee
:param status: status of the ticket(optional)
:returns : list of the tickets
schedule_meetingC
Schedule a meeting for an employee,
:param emp_id: ID of the employee
:param meeting_datetime : Date and time of the meeting in python datetime format
:param topic: Topic of the meeting
:returns : Confirmation Message
get_meetingsA
Get the list of meetings scheduled for employee
:param emp_id: ID of the employee
:returns: List of the Meetings
cancel_meetingsC
Cnacel a scheduled meeting of an employee
:param emp_id: ID of an employee
:meeting_date : Dateand time of the meeting in python datetime format
:topic : Topic of the meeting(optional)
returns :Confirmation Message
get_employee_leavesC
Get the leave balance of an Employee
:param emp_id: Id of an employee
:retuns : Remaning or the total number of leaves employee have or left
apply_leavesB
Apply for leaves for the employee
:param emp_id: ID of an employee
:leave_dates : List of leave Dates
:returns : Leave application status message
get_leave_historyC
Get the history of leaves of an Employee
:param emp_id: Id of an Employee
:returns : Leaves history messsage

Prompts

Interactive templates invoked by user choice

NameDescription
onboard_new_employee

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.7/5.0

Scored across 12 tools

Disambiguation4/5

Tools cover distinct HR areas (employee info, tickets, meetings, leaves), with clear purposes. The only ambiguity is 'send_email', which lacks description and could overlap with notifications, but overall tools are distinct.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., add_employee, get_meetings, create_ticket). Minor singular/plural variations (e.g., get_meetings vs schedule_meeting) do not detract from overall coherence.

Tool Count5/5

With 12 tools covering employee management, ticketing, meetings, and leave handling, the count is well-scoped for an HR assistant. No redundant or excessive tools.

Completeness3/5

The tool surface covers key workflows but has notable gaps: no employee update/delete, no ticket deletion, no meeting update, and no leave cancellation. These missing operations could cause agent failures in some scenarios.

Maintenance

ActivityStale
ResponsivenessNo issues