Lurna

Build an interactive flashcard deck from AI-generated Q&A pairs and open it in Lurna to study. Show an interactive flashcard deck in the MCP App UI. WORKFLOW (required): 1. When the user asks to create or generate flashcards, compose the study set yourself using the generation rules below. 2. Call this tool with user_prompt, title, description, and flashcards filled from your composed JSON. 3. The server does not generate cards and has no access to notes or external APIs — it only validates and displays what you pass. GENERATION RULES: You are a flashcard generation expert. You must return ONLY valid JSON with no additional text, markdown, or formatting. Invent concrete, accurate, pedagogically useful Q&A pairs appropriate for the topic. Stay grounded in well-established facts; avoid hallucinating obscure citations or fake specifics. If the prompt is vague, choose a reasonable scope for introductory/intermediate study material. Title: {title} Content: {content} **Card Design Principles** (Apply all of the following when generating cards): 1. Understand-first rule Never create cards for content the learner has not yet studied or that the source does not explain. A flashcard consolidates existing understanding; it does not teach new concepts from scratch. 2. Atomicity Each card tests exactly one atomic piece of knowledge. Every card should be answerable in under 6 seconds during review. If a card would regularly take longer, split it. 3. Production over recognition Cards must require the learner to produce an answer from memory, not merely recognize it. Avoid yes/no or true/false questions. Frame cards so the answer must be generated. 4. Depth of processing Wherever possible, frame questions using "why," "how," or "explain" to force elaborative reasoning rather than rote retrieval. 5. Dual coding When source material contains diagrams, graphs, or spatial information, extract all factual content from them and convert it into text-based cards. 6. Interference management After generating all cards, scan the set for pairs that are likely to be confused (similar terms, similar mechanisms, similar values). For each confusable pair, ensure at least one compare/contrast card exists that directly highlights the distinguishing feature. **Card Types** (Use a mix of the following types — select whichever best fits each piece of knowledge): 1. Definition cards (forward + reverse): For key terms. Always create both directions (term → definition AND definition → term). 2. Explain/justify cards: For concepts where understanding the reasoning matters. Answers must include the full cause-and-effect chain, not just restate the fact. 3. Compare/contrast cards: For related concepts that are commonly confused. Both sides of the comparison must appear in the answer. 4. Formula/equation cards: For mathematical relationships. Include at least one application card alongside the formula card itself. 5. Enumeration cards: When a set of items exists, prefer individual cards per item over a single list card. Never ask the learner to recall more than 3 items in a single answer. **Question framing** (use a mix): - "How does X relate to Y?" - "What would happen if...?" - "Compare X and Y" - "What are the implications of...?" - "How would you apply...?" - "Why is X important?" - "What causes / results from...?" - "Explain why [phenomenon occurs]" - "What is the equation for...?" - "[Definition or context] — what term describes this?" **Card Rules** 1. Generate enough cards to cover the topic well — typically 5–30 cards depending on complexity and source length. 2. Every card must test a distinct concept — no two cards should overlap in what they assess. 3. Answers must be 1–2 sentences maximum, crisp and self-contained. 4. Prioritize high-yield concepts: definitions of foundational terms, relationships, cause-and-effect chains, comparisons, and applications. 5. Do not repeat the question wording inside the answer. 6. Do not create diagram-dependent questions, multi-step numerical calculations, yes/no questions, or cards that list more than 3 items in the answer. **Coverage priority** 1. Definitions, laws, key equations, and core relationships 2. Explain/justify points, especially multi-step reasoning chains 3. Frequently confused pairs (generate compare/contrast cards) 4. Units, standard values, and conditions 5. Supplementary context or edge cases (only if the source emphasizes them) TITLE RULES: - Format: "[Topic] Study Set" - Description: 2-3 sentences covering what the set tests and what a student will be able to do after studying it IMPORTANT: Return ONLY valid JSON with this exact structure: {{ "title": "Study Set Title", "description": "What this set covers and its learning objectives", "flashcards": [ {{"question": "question text", "answer": "answer text"}}, {{"question": "question text", "answer": "answer text"}} ] }} Do NOT include any text before or after the JSON. Return ONLY the JSON object. No trailing commas.

create_flashcards

Create formatted Markdown study notes with an A4 reader UI and export them to Lurna. Generate structured Markdown study notes and show them in the MCP App UI (1000px wide portrait reader). WORKFLOW (required): 1. When the user asks for notes, an outline, or a study guide on a topic, compose the Markdown yourself using the rules below. 2. Call this tool with user_prompt, title, summary, and markdown filled from your composed document. 3. The server does not call an LLM — it validates, renders in the UI, and returns what you pass. GENERATION RULES: You are an expert study-notes writer and instructional designer. Your goal is to produce highly engaging, comprehensive, and well-structured Markdown notes that explain the topic with clarity and depth. USER REQUEST (verbatim): {user_prompt} SOURCE MATERIAL (if any — notes, paste, outline; otherwise invent from the topic): {content} EXTRA CONSTRAINTS: {constraints} --- ## 1. Writing Principles 1. **Pedagogical Excellence & Depth** — Do not write superficial summaries or brief overviews. Dive deep, explain the "why" and "how," and provide real context. A standard note should feel thorough and comprehensive (typically 600 to 3,000 words, depending on complexity). 2. **Adaptive Formatting (Tailor to the Subject)** — Do NOT force a single rigid template structure (like a terms table or mechanism outline) on all notes. Instead, dynamically choose the structure that best suits the topic: - **Computer Science & Coding**: Include clear code blocks with inline comments, architecture diagrams, step-by-step algorithms, and design pattern explanations. - **Mathematics & Physics**: Include equations, derivations, step-by-step proofs, and definitions of variables. - **History & Humanities**: Focus on timeline flows, historical significance, key figures, causal relationships, and thematic analysis. - **Science & Medicine**: Detail biological pathways, chemical processes, anatomical definitions, and clinical relevance. 3. **Clarity & Engagement** — Introduce complex terminology clearly, defining jargon upon its first appearance. Use formatting to break up text (bolding key terms, using bullet lists for properties), but maintain cohesive, explanatory paragraphs so the note is readable and instructional. ## 2. Dynamic Structure & Content Guide Select and arrange the following elements based on what will best help a student learn the topic. Do not include sections that do not make sense for the subject. - **Main Title**: Start the markdown with a single `#` header matching the `title` field. - **Introductory Hook / Overview**: 2-4 sentences explaining what the topic is, why it matters, and any prerequisite concepts. - **Conceptual Breakdown**: Use `##` and `###` headers to structure key concepts. Avoid flat structures. Break down the core principles, theories, or mechanisms. - **Visuals & Tables**: - Use markdown tables for comparing and contrasting related ideas (e.g., A vs. B). - Use bulleted lists or numbered steps for processes, causality chains, or algorithms. - Where appropriate, use simple Mermaid diagrams to illustrate flows or hierarchies. - **Concrete Applications & Examples**: Provide 1-3 real-world examples, case studies, or practical scenarios showing how the concepts are applied. - **Takeaway Summary**: A concise bulleted list of 3-7 key points the student must remember. - **Review / Check Yourself**: Include 2-4 simple active recall questions or reflection prompts (without immediate answers) to test comprehension. ## 3. Formatting & Tool Integration Rules - **First Line**: The markdown content must start with a single `#` title matching the `title` parameter passed to the tool. - **Headers**: Use `##` for main sections and `###` for sub-sections. Keep the hierarchy clean. - **No Outer Fences**: Do not wrap the entire returned markdown in an outer code block (e.g. ```markdown ... ```). The note should be sent as raw markdown in the `markdown` parameter. - **Tool Parameters**: Ensure you pass accurate, high-quality strings for `title`, `summary` (a 1-2 sentence preview), and the full `markdown` content.

generate_notes