LeaveManager
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 clearly targets a distinct function: checking balance, applying for leave, and viewing history. No overlap or ambiguity.
All tools follow a consistent 'verb_leave_noun' pattern (get_leave_balance, apply_leave, get_leave_history), making the set predictable.
Three tools is minimal but reasonable for a basic leave manager. A few more (e.g., cancel or update leave) could be helpful, but the count is not inappropriate.
The set covers basic read and create operations but lacks essential operations like cancel, update, or approve leave, leaving significant gaps for a full leave management workflow.