Axis LMS MCP by usefulapi

Tool purposes are mostly distinct because the resource (users, courses, ILT, learning paths, certifications, usergroups, organizations) plus the action is explicit in each name and description. The only places that could be confused are the user-lookup family (list_users vs search_users vs count_users) and the certification reporting tools, but the descriptions state the differences clearly enough to choose correctly.

Every tool uses the axislms_ prefix with snake_case verb_noun form (list_courses, get_user, enroll_user_in_course, unenroll_user_from_ilt_session). The report tools use a noun_report suffix instead of a leading verb, which is a small but consistent deviation. The convention is predictable, so an agent can guess names.

44 tools is heavy, but the server spans eight resource families (users, courses, ILT, paths, certifications, usergroups, organizations, reports), each needing roughly 4-6 operations. Each tool covers a different endpoint, so the set is mostly justified, but there is a lot of surface to navigate and some list and report tools could be consolidated.

Read coverage is thorough (lists, gets, counts, and five report types), and enrollment and usergroup membership lifecycles are complete with enroll and unenroll pairs. However, write coverage is thin: there is no create, update, or delete for courses, learning paths, ILT programs or sessions, certifications, or organizations, and no get_learningpath or get_ilt_session single-item lookup, which will block setup and maintenance workflows.