MCP server for managing employee leave balances and leave applications
Three tools with basic verb-noun naming (get_*, apply_*) and present descriptions, but significant gaps in parameter documentation, output schema clarity, and error handling. All tools lack parameter descriptions beyond the bare parameter name. Descriptions are present but generic (10-50 chars, below the 50-200 char LLM-optimized baseline). No output schemas documented. Error messages are plain strings with no recovery guidance. Mock data and lack of input validation suggest early-stage implementation.
Apply leave for specific dates (e.g., ["2025-04-17", "2025-05-01"])
Check how many leave days are left for the employee
Get leave history for the employee
Parameter descriptions missing. All three tools have parameters (employee_id, leave_dates) with no descriptions in the schema. LLMs cannot infer parameter meaning from names alone.
Output schemas not documented. Tools return plain strings (e.g., 'E001 has 18 leave days remaining.') with no structured schema. LLMs cannot extract fields for downstream tool chaining.
Error messages lack recovery guidance. 'Employee ID not found' and 'Insufficient leave balance' do not tell the LLM what to do next (e.g., 'Try search_employees() first').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | 2026-07-28+ | v2 |
Descriptions too short (10-50 chars vs. 50-200 char baseline). 'Check how many leave days are left for the employee' lacks context on when to use this vs. get_leave_history, and does not explain the return format.
No input validation or constraints. apply_leave accepts any string dates without format validation (ISO 8601?). No min/max on leave_dates array length. LLMs can pass invalid input without guidance.