leave-manager-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_leave_balanceC | Check how many leave days are left for the employee |
| apply_leaveB | Apply leave for specific dates (e.g., ["2025-04-17", "2025-05-01"]) |
| get_leave_historyC | Get leave history for the employee |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct aspect of leave management: balance inquiry, applying for leave, and viewing history. There is no overlap in purpose or output.
All tool names follow a clear verb_noun pattern: get_leave_balance, apply_leave, get_leave_history. The naming is predictable and consistently structured.
With 3 tools, the server is well-scoped for a simple leave management use case. Each tool serves a clear need without unnecessary bloat.
The tool set covers the basic employee-facing actions (check balance, apply, view history), but it lacks an update or cancellation operation for leave requests. This is a notable gap in the lifecycle.