Daily Tutor MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TUTOR_TZ | No | Default IANA timezone (per-user override with set_settings). Decides when "today" starts. | system |
| TUTOR_HOST | No | HTTP bind address. | 127.0.0.1 |
| TUTOR_PORT | No | HTTP bind port. | 8000 |
| TUTOR_DATA_PATH | No | Folder for the SQLite database (defaults to ~/.daily-tutor, or /data in Docker). | ~/.daily-tutor |
| TUTOR_TRANSPORT | No | Transport mode: stdio or streamable-http (defaults to stdio, or streamable-http in Docker). | stdio |
| TUTOR_API_TOKENS | No | Required for HTTP transport. Comma-separated token:user pairs, e.g. token:user,token:user. | |
| TUTOR_PUBLIC_URL | No | Public URL when behind a proxy. | http://localhost:8000 |
| TUTOR_ALLOWED_HOSTS | No | Comma-separated hostnames; enables DNS-rebinding protection. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| set_preferencesB | SETUP: replace the user's topic list. Topics are chosen BY THE USER, can be anything and several at once (e.g. ["sysadmin", "devops", "network engineer"]). All get the same starting level (it adapts later). Afterwards propose 6-10 subtopics per topic and save them with set_topic, or offer a certification track (list_tracks). |
| set_topicA | Add or update ONE topic: its level, its subtopics (replaces the list), and whether the level adapts automatically (auto_adjust). Setting a level manually restarts adaptation from now. |
| remove_topicB | Drop one topic (history is kept). |
| set_question_typesC | Choose which question types the user wants (empty list = all). |
| list_question_typesB | All question types: how to write them, how the user answers, how they are graded. |
| set_settingsB | Set the daily XP goal (default 20) and/or the user's IANA timezone (e.g. 'Europe/Kyiv'). The timezone decides when 'today' starts, which matters for streaks. |
| get_preferencesC | Topics (level, auto-adjust, subtopics), question types, goal, timezone, data location. If configured is false, run SETUP: ask which topics (any, several allowed) and level. |
| list_tracksA | Certification/learning tracks the user can start (exam objectives become subtopics). |
| start_trackA | Add a certification track as a topic; its objectives become subtopics so get_coverage can show which objectives are still untouched. |
| add_materialB | Store the user's own material (notes, runbook, postmortem, docs) so some questions are grounded in it. Content is split into chunks of about 1500 characters. topics = which of the user's topics it belongs to (empty = any). |
| list_materialsC | The user's stored materials. |
| remove_materialC | Delete a stored material. |
| start_sessionA | Start a lesson of n questions (default 5, max 20) asked one at a time, ending with a summary. Then loop: get_next_question_brief(session_id) -> write -> save_question -> user answers -> check_answer/record_result -> next, until the session reports done. |
| get_sessionC | Progress of a session (and its summary once finished). |
| get_next_question_briefA | ASK step 1. Returns exactly what to write: topic(s), subtopic, level, question TYPE, writing instructions, the REQUIRED answer position, and what to avoid. Overdue spaced-repetition reviews are served first (alternating with new questions). Optional: topic = user asked for one topic now; from_material = ground the question in the user's own material. Write ONE question, then store it with save_question. Never reveal the answer. |
| save_questionA | ASK step 2: store the question you wrote. Use the topics/qtype from the brief and put the correct answer where the brief REQUIRED it (answer_key must match required_answer_key). concept = 2-6 word tag of the single idea tested. correct_answer = readable answer text. key_points = what a good free-text answer contains. The server rejects duplicates and wrong answer positions: fix and resend. Then show the user ONLY the question + reply format. |
| get_pending_questionB | The latest unanswered question with its answer key and grading guide (for you, not the user). |
| check_answerA | EVALUATE step 1: ALWAYS call this first with the user's raw reply. For letters, ordering, matching, true/false verdicts and accepted commands it grades exactly and records XP/streak itself (auto_graded=true): then just explain. Otherwise (auto_graded=false) it tells you how to judge, and you finish with record_result. bad_format=true means ask the user to reformat; the question stays open. |
| record_resultA | EVALUATE step 2 (only when check_answer said auto_graded=false): record 'correct', 'partial' or 'wrong'. Awards XP, updates streak, schedules spaced repetition, adapts the level. Then explain why the right answer is right, why the tempting wrong one fails, and add one real-world gotcha. |
| use_hintB | The user asked for a hint. Returns it; XP for this question is halved. |
| skip_questionC | The user skipped the question: no XP, no streak. Counts toward a session's length. |
| review_mistakesC | Past wrong/partial answers with the right answer and explanation, newest first. |
| get_due_reviewsC | Spaced-repetition queue: what is due now and what is coming in the next 7 days. |
| get_progressB | XP, streak (with freezes), daily goal, accuracy per topic and per question type, weakest topic/type, review queue. Use for 'how am I doing?' / 'where is my progress?'. |
| get_coverageB | Objective coverage for one topic (great for certification tracks): which subtopics are untouched, which are weak, and the overall coverage %. |
| weekly_recapB | Data for a weekly recap: this week vs last week (questions, accuracy, XP, active days), topic deltas, improved/weakest areas, streak, reviews mastered. Write the recap yourself. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily_question | The scheduled/cron 'daily question' prompt. |
| quiz_session | Start a lesson of n questions. |
| recap | Weekly recap. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 26 tools
Most tools map to a clearly distinct step in a well-signposted workflow (SETUP, ASK step 1/2, EVALUATE step 1/2), and descriptions explicitly say when to use which. The main friction points are the config cluster (set_preferences vs. set_topic vs. set_settings) and the analytics cluster (get_progress vs. get_coverage vs. weekly_recap), where boundaries are clear only after reading the detailed descriptions.
Predominantly a consistent snake_case verb_noun pattern (set_topic, get_session, save_question, check_answer, remove_material). A few deviations exist, notably use_hint and weekly_recap which lack a clarifying verb, and the very long get_next_question_brief, but nothing is ambiguous or chaotically mixed.
26 tools is on the heavy side; while the domain (setup, materials, sessions, question authoring, grading, spaced repetition, analytics) legitimately spans many stages, several tools are fine-grained splits that could be consolidated. The check_answer/record_result and get_next_question_brief/save_question pairs in particular feel like protocol steps rather than standalone capabilities.
The lifecycle is well covered: onboarding, topic/track management, material ingestion, session flow, question generation, grading, spaced repetition, mistakes review, and analytics. Minor gaps exist, such as no way to abandon/reset a session or edit a previously saved question, but agents can work around these.