HR (RH) Copilot — MCP Server demonstrating Tools, Resources, and Prompts for HR management workflows including vacation approvals, employee requests, and HR policy access
This educational MCP server demonstrates basic tool patterns but falls well short of production quality. Five tools are present with varying levels of definition. While tool names follow verb-noun conventions and descriptions exist, critical gaps emerge in schema completeness, parameter documentation, and error handling guidance. The `ping` tool is trivial (no params, no validation). The four substantive tools (`aprovar_ferias`, `criar_solicitacao`, `enviar_resposta`, `transferir_departamento`) have descriptions but lack comprehensive parameter validation, enum constraints, and error recovery guidance. No tool returns documented output schemas or pagination info. Error handling is minimal, responses indicate success/failure but do not guide the LLM on remediation steps. The codebase shows mock in-memory data with hardcoded employee lists; no production integration, no input sanitization, no rate limiting, no audit logging, and no security boundary enforcement.
Aprova solicitação de férias de um colaborador. Recebe o ID do colaborador e o período desejado. Valida se o colaborador existe e retorna confirmação com protocolo.
Cria uma nova solicitação no sistema de RH. Tipos válidos: ferias, abono, transferencia, desligamento. Prioridades válidas: baixa, media, alta, urgente. Use quando o usuário pedir para criar ou abrir uma nova solicitação.
Envia uma resposta formal por email para um colaborador. Recebe o ID do colaborador e o texto da mensagem. Use quando o usuário pedir para enviar uma comunicação ou resposta.
Verifica se o server está ativo
Transfere um colaborador para outro departamento. Atualiza o departamento do colaborador no sistema de RH. Use quando o usuário pedir para mover ou transferir um colaborador para um novo departamento ou equipe.
No documented output schemas across any tool. LLMs cannot know what fields to expect, making downstream chaining impossible and forcing parsing of unstructured responses.
Parameters lack enum constraints and validation rules. 'tipo' in criar_solicitacao lists valid values in description ('ferias, abono, transferencia, desligamento') but not as a machine-readable enum. 'prioridade' similarly underconstrained. LLMs will guess at valid values.
Error responses do not guide recovery. Example: 'Colaborador {id} não encontrado', no suggestion to search first or what to do next. Violates recovery-guide pattern.
Date parameters (data_inicio, data_fim) lack format documentation. Code assumes YYYY-MM-DD but description does not enforce it. LLMs will pass invalid formats.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 47 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 45 | - | v1 |
No audit trail or logging of tool invocations. Critical for HR systems handling employee data, who accessed what, when, and with what input is untracked.
No permission gates on destructive operations. criar_solicitacao and transferir_departamento modify HR records but do not verify the caller has write:rh or equivalent scope. Mock data makes this moot now, but production risk is severe.
Responses include raw mock data fields (e.g. 'notificacao_enviada': True in aprovar_ferias) with no structure definition. A production API might return 50+ metadata fields; unclear which are meaningful.
No idempotency or dry-run support for irreversible operations like 'aprovar_ferias' or 'enviar_resposta'. Agents should be able to preview before sending.