Tutorials/Github-Copilot-VSCode-MCP.md

@@ -105,12 +105,12 @@ For example, I used MCP servers for literature research:
 
 - **arxiv-mcp-server**  
   Provides access to arXiv papers by ID or query.  
-  *Example:* I used it to make literature research and download papers automatically. E.g. "Download all papers of <Researcher-name> of the past X years".  
+  *Example:* E.g. "Download all papers of *Researcher-name* of the past X years".  
 
 - **markitdown**  
   Converts documents between formats (e.g., PDF → Markdown). Useful to give agents the capabilities to read documents (Reading PDFs often fails).  
   *Example:* Convert each downloaded Arxiv paper to markdown and write a one-page summary of the paper. 
-  --> Follow-up instruction: Write a markdown in which you provide an overview how the research of <Researcher-name> evolved over the past X years. 
+  --> Follow-up instruction: Write a markdown in which you provide an overview how the research of *Researcher-name* evolved over the past X years. 
 
 - **sequentialthinking**  
   Helps structure reasoning or workflows step by step.  
@@ -119,19 +119,19 @@ For example, I used MCP servers for literature research:
 
 # Further thoughts about MCPs
 
-### 5. Quick Comparison: Copilot vs. Gemini
+### Quick Comparison: Copilot vs. Gemini
 - Speed: Copilot often snappier; Gemini better for long-form, big-context reasoning.
 - Cost: Copilot 10€/month, Gemini free
 - VSCode integration: GitHub Copilot + , Gemini -
 
 Personal Preference: I prefer GitHub Copilot integrated in VSCode and using it for small incremental coding tasks instead of Gemini CLI or Claude Code CLI. Giving too much control to an agent still feels scary, especially with the errors I encountered with Gemini (Hallucinations!).
 
-### 6. Core Workflows
+### Core Workflows
 - RAG: PDF → Markdown → select → summarize / code.
 - Research: arXiv search → download → summarize → markdown.
 - Refactor: fetch upgrade guide → plan (sequential tool) → apply edits.
 
-### 7. Best Practices
+### Best Practices
 - Restrict where writes can occur to prevent accidental damage.
 - Keep the number of MCPs low! Only 4-5 MCPs per agent otherwise the agent gets overwhelmed and slows down.
 - Start with one tool; Don’t wire up many MCP tools at once; pick the one that gives the biggest lift (e.g., PDF→Markdown).
@@ -139,7 +139,7 @@ Personal Preference: I prefer GitHub Copilot integrated in VSCode and using it f
 - Provide outline/TOC tool before full content loads. Tell the agent to ask if it understood the instructions correctly and ask permission before each subtask. 
 - CHECK THE RESULTS IN DETAIL! 
 
-### 8. Common Pitfalls
+### Common Pitfalls
 - “God” tool doing everything (hard to evolve/control).
 - Unbounded output → token exhaustion (Can be very expensive depending on the MCP server)!