Leave Management MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEMINI_API_KEY | Yes | API key for Google Gemini integration |
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_balanceD | – |
| apply_leaveD | – |
| get_leave_historyD | – |
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 covers a distinct aspect: balance inquiry, leave application, and history lookup. There is no overlap or ambiguity between them.
All tool names follow the consistent verb_noun pattern: get_leave_balance, apply_leave, get_leave_history. The naming is clear and predictable.
Three tools are well-scoped for a simple leave management server, covering the core employee-facing actions without unnecessary bloat.
Core leave lifecycle is covered (check balance, apply, view history), but missing operations like cancel or update leave applications are notable gaps.