No user-submitted related servers found.
Scored across 27 tools
The tool set uses clear domain segments (clock, monthly, personal_application, approval), and every prepare/commit pair is explicitly documented as read/preview vs. actual write. However, the high number of similar 'prepare_action'/'commit_action' names—especially monthly_prepare_action vs. monthly_approval_prepare_action—means an agent must rely heavily on descriptions to avoid misselection.
Names follow a consistent freee_<domain>_<operation> snake_case pattern with predictable status/list/detail/options/prepare/commit vocabulary. Minor inconsistencies like freee_me and the plural/singular alternation between freee_personal_applications_list and freee_personal_application_detail keep it from a perfect score.
At 27 tools, the surface exceeds the 25-tool 'too many' threshold. The prepare/commit safety split doubles the number of tools for what are often the same logical actions, making the set feel heavy even though the underlying HR workflow is broad.
The server covers the main employee application lifecycle (create, read, cancel, withdraw), clock punches, monthly attendance submission, and approval/return workflows with strong safety checks. It still lacks a direct update/edit tool for personal applications and an explicit punch-history read, though these are minor gaps.