Related Servers

Each tool has a clearly distinct purpose with no overlap: add-tool-annotation modifies tool metadata, build-toolset creates custom sets, delete-toolset removes saved sets, equip-toolset activates a set, get-active-toolset retrieves current set info, list-available-tools discovers all tools, list-saved-toolsets shows saved configurations, and unequip-toolset deactivates the current set. The descriptions clearly differentiate between creation, management, activation, and discovery operations.

All tools follow a consistent verb-noun pattern with hyphen separation: add-tool-annotation, build-toolset, delete-toolset, equip-toolset, get-active-toolset, list-available-tools, list-saved-toolsets, unequip-toolset. The naming convention is perfectly uniform throughout the set, making it easy to understand each tool's function from its name alone.

With 8 tools, this is well-scoped for a toolset management server. Each tool earns its place by covering distinct aspects of the domain: tool annotation, toolset creation, deletion, activation, status checking, tool discovery, saved toolset listing, and deactivation. The count is neither too sparse nor bloated for managing custom tool configurations.

The tool surface provides complete CRUD/lifecycle coverage for toolset management: create (build-toolset), read (get-active-toolset, list-available-tools, list-saved-toolsets), update (add-tool-annotation modifies tool behavior), and delete (delete-toolset). It also covers activation/deactivation (equip-toolset, unequip-toolset) and discovery operations, leaving no obvious gaps for managing custom toolsets.