refactor: replace console logging with notification messages in sampling exercises

Author: kentcdodds

exercises/01.advanced-tools/01.problem.annotations/src/index.ts

@@ -18,6 +18,7 @@ export class EpicMeMCP {
 				tools: {},
 				resources: {},
 				completions: {},
+				logging: {},
 				prompts: {},
 			},
 			instructions: `

exercises/01.advanced-tools/01.solution.annotations/src/index.ts

@@ -18,6 +18,7 @@ export class EpicMeMCP {
 				tools: {},
 				resources: {},
 				completions: {},
+				logging: {},
 				prompts: {},
 			},
 			instructions: `

exercises/01.advanced-tools/02.problem.structured/src/index.ts

@@ -18,6 +18,7 @@ export class EpicMeMCP {
 				tools: {},
 				resources: {},
 				completions: {},
+				logging: {},
 				prompts: {},
 			},
 			instructions: `

exercises/01.advanced-tools/02.solution.structured/src/index.ts

@@ -18,6 +18,7 @@ export class EpicMeMCP {
 				tools: {},
 				resources: {},
 				completions: {},
+				logging: {},
 				prompts: {},
 			},
 			instructions: `

exercises/02.elicitation/01.problem/src/index.ts

@@ -18,6 +18,7 @@ export class EpicMeMCP {
 				tools: {},
 				resources: {},
 				completions: {},
+				logging: {},
 				prompts: {},
 			},
 			instructions: `

exercises/02.elicitation/01.solution/src/index.ts

@@ -18,6 +18,7 @@ export class EpicMeMCP {
 				tools: {},
 				resources: {},
 				completions: {},
+				logging: {},
 				prompts: {},
 			},
 			instructions: `

exercises/03.sampling/01.problem.simple/README.mdx

@@ -24,7 +24,7 @@ prompt for the LLM in the next step.
   message that references the new journal entry's ID (we'll enhance this next).
 - Set a reasonable `maxTokens` value for the response.
 - Parse the model's response using a provided Zod schema.
-- Log the result to the console so you can inspect the model's output.
+- Send a notification with the result so you can see the model's output.
 
 And don't forget to call it when the user creates a new journal entry!
 
@@ -68,6 +68,23 @@ The `maxTokens` option references the max tokens the model should return.
 	window size of the model you're user is using.
 </callout-warning>
 
+Here's an example of how to send a notification:
+
+```ts
+// void is to communicate we don't care about the return value. Fire and forget.
+void agent.server.server.sendLoggingMessage({
+	level: 'info', // "error" | "debug" | "info" | "notice" | "warning" | "critical" | "alert" | "emergency"
+	// data can be any JSON-serializable value
+	data: {
+		a: 1,
+		otherStuff: '...',
+	},
+})
+```
+
+Check the specification for more info:
+https://modelcontextprotocol.io/specification/2025-06-18/server/utilities/logging#log-message-notifications
+
 This step will help you get comfortable with the basic request/response flow for
 sampling in MCP, and set the stage for more advanced prompt engineering in the
 next step.

exercises/03.sampling/01.problem.simple/src/index.ts

@@ -18,6 +18,7 @@ export class EpicMeMCP {
 				tools: {},
 				resources: {},
 				completions: {},
+				// 🐨 add the `logging` capability to the `capabilities` object
 				prompts: {},
 			},
 			instructions: `

exercises/03.sampling/01.problem.simple/src/sampling.ts

@@ -10,5 +10,7 @@ export async function suggestTagsSampling(agent: EpicMeMCP, entryId: number) {
 	// 🐨 Add a user message with the content "You just created a new journal entry with the id ${entryId}. Please respond with a proper commendation for yourself."
 	// 🐨 Set the maxTokens what you think is reasonable for the request
 	//
-	// 🐨 add a console.error to print the result.content.text (this will show up in the inspector)
+	// 🐨 logging message to send the model response to the client
+	// 📜 https://modelcontextprotocol.io/specification/2025-06-18/server/utilities/logging#log-message-notifications
+	// 💰 agent.server.server.sendLoggingMessage (with level of 'info', logger of 'sampling', and data with the model response)
 }

exercises/03.sampling/01.solution.simple/src/index.ts

@@ -18,6 +18,7 @@ export class EpicMeMCP {
 				tools: {},
 				resources: {},
 				completions: {},
+				logging: {},
 				prompts: {},
 			},
 			instructions: `