Related Servers

Massive overlap between tools: list-allocations/delete-allocation/create-allocation/update-allocation duplicate list-tasks/update-task/delete-task/create-task since allocations and tasks are the same Float API entity. Additional confusion from manage-entity and manage-project-workflow consolidated tools that overlap with nearly every CRUD tool, and duplicate timeoff/time-off-type tools.

Naming is highly inconsistent: some use 'timeoff' (list-timeoff, create-timeoff) while others use 'time-off' (list-time-off-types, create-time-off-type). Conventions mix verb-object and object-verb patterns (get-project-tasks-by-project vs list-project-tasks, delete-allocation vs list-allocations). No clear consistent prefix or pattern emerges.

With 136 tools, this is an extreme case of over-proliferation. Even accounting for Float's broad API surface, the count is excessive and would overwhelm any agent. The presence of redundant consolidated tools (manage-entity, manage-project-workflow) alongside granular CRUD tools compounds the problem.

The tool surface is quite thorough for Float's domain, covering projects, tasks, phases, milestones, time off, holidays, logged time, people, accounts, roles, departments, clients, and reports. Minor gaps exist around some specialized operations, but overall coverage is comprehensive.