Namely MCP by usefulapi

Each tool has a distinct resource/action target: profiles, groups, teams, events, comments, job titles/tiers, profile fields, and reports are clearly separated. The list/get variants are unambiguous because their descriptions explain collection versus single-record access, and update_profile versus get_profile is clearly distinguished by write semantics.

All tools use a consistent snake_case pattern with the namely_ prefix followed by verb_noun, such as namely_list_profiles, namely_get_group, and namely_create_announcement. Minor idiomatic names like namely_get_me do not break the pattern.

At 17 tools the set is slightly above the typical 3-15 range, but each tool maps to a distinct Namely resource and appears to earn its place. There is no obvious filler or redundant endpoint duplication.

The surface covers broad read access across profiles, groups, teams, events, job structures, fields, and reports, plus profile updates and feed posting. However, it lacks several lifecycle operations such as creating/deleting profiles, managing groups/teams, listing reports, and mutating job titles or tiers, and namely_get_report requires an externally discovered report id.