Learn Shell
Related Servers
Alternatives to Learn Shell
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables AI agents to act as a state-driven tutoring engine over MCP, with server-side mastery estimation, prerequisite checks, evidence-based assessment, and FSRS spaced review scheduling.581MIT
- FlicenseNot gradedqualityDmaintenanceA multi-agent AI tutor that delivers personalized lessons, resolves doubts with RAG, generates quizzes, and tracks progress, all accessible via MCP for Claude Desktop.5-
- AlicenseAqualityAmaintenanceEnables AI agents to share, search, and learn from structured lessons, ask and answer questions asynchronously, and contribute to a shared knowledge commons via MCP.194 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create and manage personalized 30-day study courses, including web research with source validation, daily lessons, quizzes, and progress tracking through 12 MCP tools.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to generate teaching materials such as PPTs, handouts, lecture scripts, mind maps, teaching video storyboards, and Manim math animations, plus run quality checks and language normalization through 15 MCP tools.MIT
- AlicenseNot gradedqualityAmaintenanceA local-first study workspace for MCP agents, providing a web UI for learning, quizzing, and review, independent of agent lifecycle.4GPL 3.0
TDQS
Scored across 50 tools
Each tool targets a distinct resource/action combination, even within dense families like add/update/record. Closely related tools such as add_lesson_patch and update_lesson have clearly defined boundaries based on lesson progress state. The overlap risk is minimal despite the large surface.
Most tools follow a verb_noun pattern (add_lesson, create_course, get_context), but the live_* and adhoc_* families invert this to noun_verb (live_message_send, adhoc_thread_get) or use ambiguous nouns like live_pending. This creates a noticeable inconsistency, though each family is internally consistent.
At exactly 50 tools, the server is at the extreme end of the scale and falls into the '50+ tools' criterion. Even for a complex tutoring platform, the surface is unwieldy and likely to increase selection latency and cognitive load for agents. A more curated set of 20-30 tools would be far more appropriate.
The toolset covers the full lifecycle: pair creation, contract negotiation, course/lesson authoring, exercise grading, live session management, feedback loops, and reflection. Minor gaps exist (e.g., no update/delete for courses, no direct list-all lessons), but overview tools like get_context and get_teacher_inbox make these workable.