Study Errorbook
Related Servers
Alternatives to Study Errorbook
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI chat clients to extract exam papers and academic documents into a structured, source-traceable representation once, then retrieve, verify and export it as JSON, Markdown, searchable PDF, DOCX, LaTeX or CSV/XLSX without re-running OCR. The connected client's own model transcribes page images in host mode, so no API key is required, while deterministic text-layer extraction, preprocessing, validation and uncertainty labelling happen server-side.1MIT
- AlicenseBqualityBmaintenanceEnables MCP-compatible AI clients to act as a personal exam-prep tutor for Chinese postgraduate entrance exams, with a local knowledge base, spaced-repetition review scheduling, worksheet generation and delivery (print/PDF/HTML/text), and learning analytics—all with zero third-party dependencies and data staying local.142MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable agents to query a fine-grained computer-science exam knowledge-point graph, map questions to knowledge points, diagnose broken cross-subject links and weak areas, retrieve reviewed analogies, and import user-supplied exam PDFs into a traceable question bank.MIT
- AlicenseBqualityCmaintenanceEnables deterministic IELTS answer checking, evidence-grounded explanations, error-cause classification, spaced repetition of mistakes, and progress reports, with data stored locally.10MIT
- AlicenseAqualityBmaintenanceConnects AI assistants to a medical question bank so students can search exam questions, generate and grade mock exams with detailed explanations, and track their weakest topics. Answer keys are withheld until grading, keeping practice honest.6MIT
- AlicenseNot gradedqualityDmaintenanceProvides a local CBT exam system as MCP tools for Codex, managing study sessions, scoring, wrong answer tracking, and review queues with deterministic Python engine and optional Notion integration.MIT
TDQS
Scored across 32 tools
The toolset spans distinct stages, but several read/query tool families overlap significantly (read_document vs read_element vs read_evidence vs read_element_evidence; read_practice_feedback vs read_practice_history). Their descriptions are detailed and help, yet the sheer number of superficially similar 'read_*' and 'list_*' tools creates real misselection risk.
Almost all tools use snake_case with a verb_noun pattern (import_document, read_study_record, update_review_plan), which is predictable. Minor deviations like workspace_status (noun phrase) and compound names such as resume_job_observation keep it from perfect consistency.
32 tools far exceed the typical well-scoped range of 3–15 and land in the 'too many' bucket per the rubric. Although each tool maps to a real sub-operation in a complex study-errorbook workflow, the volume imposes substantial cognitive load and coordination burden.
The surface covers import, OCR parsing, evidence extraction, study-record CRUD, practice recording/history, review planning, and export—a broad lifecycle. Only minor gaps remain, such as explicit parse-job cancellation or bulk study-record management, which agents can likely work around.