TrackingTime

Most core CRUD tools are distinct, but event/time queries overlap heavily (list_events, list_company_events, list_filtered_events, advanced_search, get_events_stats/summary) and the render_* family contains many similarly purposed presentation tools. Descriptions help, but an agent must read carefully to avoid misselection.

The set mostly follows a clear snake_case verb_noun convention: list_, get_, create_, update_, delete_, archive_, restore_, assign_, render_, etc. Minor deviations include advanced_search lacking a verb, add_task_comment using add while task CRUD uses create, and mixed singular/plural in batch tool names.

138 tools is far beyond an appropriate MCP surface, even for a broad time-tracking/project-management domain. The volume creates overwhelming choice and redundancy, and the rubric explicitly treats 50+ tools as an extreme mismatch.

Lifecycle coverage is unusually broad across tasks, projects, customers, events, invoices, expenses, time off, schedules, users, custom fields, reports, and rendering. Some secondary gaps exist, such as no update operation for task comments and limited expense-category management, but most core workflows are covered.