mcp-student-leave-copilot-ab
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_studentsA | Return all students with remaining leave balance. |
| get_student_detailsA | Return one student and their leave requests. |
| approve_leaveC | Approve a pending leave and update balance. |
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 has a clearly distinct purpose: listing all students, fetching a single student's details, and approving a leave. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern: list_students, get_student_details, approve_leave. The naming style is uniform and predictable.
Three tools is well-scoped for a focused student leave copilot, each serving a distinct function without redundancy. The count is within the ideal 3-15 range.
The core workflow of viewing students and approving leave is covered, but there is no reject or batch approval capability. Minor gaps exist, but they are workaroundable by iterating through students.