No user-submitted related servers found.
Scored across 16 tools
Most tools have a clearly distinct target: session management vs. course listings vs. per-lesson artifacts (slides, replay, mind map, notes, score). However, ykt_lesson and ykt_lesson_summary overlap substantially (both return the courseware list for a lesson), and announcements can be reached through both ykt_activities (type=9) and ykt_discussion, forcing the agent to guess. These few overlaps are mitigated by descriptions that hint at the intended use, but boundaries are not airtight.
All 16 tools share a uniform `ykt_` prefix and snake_case body, so the set reads predictably. The bodies are noun-oriented (ykt_courses, ykt_slides, ykt_score) rather than the verb_noun pattern, with a handful of verb-style names (ykt_login, ykt_logout), but there are no mixed casing conventions or erratic verb styles.
16 tools is on the high side but each maps to a genuine artifact of the learning platform (session, courses, activities, lessons, slides, replay, mind map, notes, score, progress, live, discussion, classroom). The only clearly redundant slot is ykt_lesson_summary, which largely restates ykt_lesson. Scope is otherwise defensible for a domain this rich.
Within the declared read-only scope, coverage is strong: auth lifecycle (login/status/logout), course discovery, activity enumeration, per-lesson resources, progress tree, and live overview. Dead ends exist — quiz/question content is explicitly null from ykt_slides, and there is no write path (no sign-in, no homework submission), which is a deliberate limitation but limits the surface for an agent trying to complete coursework.