diff --git a/typescript/animal-rescue-mcp-server/images/claude_animal_rescue-450x400.gif b/typescript/animal-rescue-mcp-server/images/claude_animal_rescue-450x400.gif
new file mode 100755
index 0000000..a240d69
Binary files /dev/null and b/typescript/animal-rescue-mcp-server/images/claude_animal_rescue-450x400.gif differ
diff --git a/typescript/animal-rescue-mcp-server/images/claude_list_animals_tool-450x400.gif b/typescript/animal-rescue-mcp-server/images/claude_list_animals_tool-450x400.gif
new file mode 100755
index 0000000..1a800b9
Binary files /dev/null and b/typescript/animal-rescue-mcp-server/images/claude_list_animals_tool-450x400.gif differ
diff --git a/typescript/animal-rescue-mcp-server/part-1-instructions.md b/typescript/animal-rescue-mcp-server/part-1-instructions.md
index 1c2dbd8..7e77eee 100644
--- a/typescript/animal-rescue-mcp-server/part-1-instructions.md
+++ b/typescript/animal-rescue-mcp-server/part-1-instructions.md
@@ -3,13 +3,13 @@
 
 Welcome! In this workshop, we’ll explore what an MCP server is, how it connects to AI models like Claude, and how to use tools and prompts to build a smart backend — all while helping match humans with adoptable pets 🐕🐍🐔
 
-You’ll be using the **TypeScript MCP SDK**, but don’t worry — this workshop is about understanding **how MCP servers work**, not mastering every line of code.
+You’ll be using the **TypeScript MCP SDK**, but don’t worry if you're not familiar with **TypeScript** — this workshop focuses on understanding  **how MCP servers work**, not mastering the code 😉.
 
 ---
 
 ## 🧩 Part 1: Set Up Your Server & List Animals
 
-### 1. 🚀 Clone the repo via your command line of choice
+### 1. 🚀 Clone the repo via your terminal/command line of choice
 
 ```bash
 git clone https://github.com/DevOps-Represent/mcp-server-workshop.git
@@ -24,8 +24,8 @@ In the `src` folder you'll find:
 * 📄 `index.ts`: Your main entry point — this starts your server and registers the tools - this is where you'll be working the most.
 * 📄 `animal-rescue-service.ts`: This file contains some pre-built logic for the workshop — like functions to get animal data and schemas that describe what a valid animal looks like.
   * We’ve already defined things like:
-    * animalSchema: What each animal object includes (name, type, medical needs, etc.)
-    * AnimalRescueService: A helper class with methods to list animals, find them by name or ID, and simulate adoptions.
+    * **animalSchema**: What each animal object includes (name, type, medical needs, etc.)
+    * **AnimalRescueService**: A helper class with methods to list animals, find them by name or ID, and simulate adoptions.
 * 📄 `animal-data.ts`: Static JSON-like data that contains info on adoptable pets
 
 #### Imports
@@ -36,22 +36,22 @@ In the `src` folder you'll find:
 import { McpAgent } from "agents/mcp";
 ```
 
-McpAgent is a wrapper built around the MCP SDK tools, designed to simplify building your own MCP server. It’s not part of the SDK itself, but it uses the SDK under the hood.
+**McpAgent** is a wrapper built around the **MCP SDK tools**, designed to simplify building your own **MCP server**. It’s not part of the SDK itself, but it uses the SDK under the hood.
 
-MyMCP (your class) → McpAgent (custom wrapper) → MCP SDK tools (McpServer, etc.)
+**MyMCP** (your class) → **McpAgent** (custom wrapper) → **MCP SDK tools** (McpServer, etc.)
 
 ```ts
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 ```
 
-McpServer: This is the actual server that communicates with Claude (or another MCP-compatible client).
+**McpServer**: This is the actual server that communicates with **Claude** (or another MCP-compatible client).
 It listens for requests, manages tool registration, and handles sending back structured responses.
 
 ```ts
 import { z } from "zod";
 ```
 
-z: This is from the Zod library — used to define and validate input/output schemas for your tools.
+**z**: This is from the Zod library — used to define and validate input/output schemas for your tools.
 Helps ensure that your client sends structured data you can work with (and avoids weird bugs).
 
 ```ts
@@ -64,9 +64,9 @@ import {
 
 We've done some work to create the animal rescue service, so you're not creating is from scratch. Importing the following means we focus more on the mcp server set up and less about the animal rescue service creation!
 
-* AnimalRescueService: A helper class that contains all the logic for managing pets — listing them, looking them up, simulating adoptions, etc.
-* animalSchema: A Zod schema that describes what a valid animal object looks like (e.g., name, type, home requirements).
-* adoptionCertificateSchema: Another Zod schema — likely used for generating structured confirmation when a pet is adopted (e.g., name, date, adopter).
+* **AnimalRescueService**: A helper class that contains all the logic for managing pets — listing them, looking them up, simulating adoptions, etc.
+* **animalSchema**: A Zod schema that describes what a valid animal object looks like (e.g., name, type, home requirements).
+* **adoptionCertificateSchema**: Another Zod schema — likely used for generating structured confirmation when a pet is adopted (e.g., name, date, adopter).
 
 #### 📥 How Your MCP Server Handles Incoming Requests (Cloudflare example)
 
@@ -90,29 +90,25 @@ export default {
         .fetch(request, env, ctx);
     }
 
-    return new Response("Not found", { status: 404 });
+    return new Response("MCP server active 🤖. Connect via MCP protocol at /mcp or /sse.", { status: 404 });
   },
 };
 ```
 
-**🧠 What This Is Doing Using a Cloudflare playground version**
-
-This section is what your mcp client uses to decide how to route incoming HTTP requests to the right part of your MCP server.
-
-🧩 Let’s break down what each part does:
+##### 🧩 Let’s break down what each part does:
 
 - **🔁 fetch(...)**
 
-  - This is the main handler. Every time a request comes into your server, it runs this function.
+  - This is the main handler. Every time a request comes into your server, it runs this function to handle incoming requests.
 
 - **✅ const url = new URL(request.url);**
 
-  - Parses the request so we can check what the URL path is (like /sse or /mcp).
+  - Parses the request so we can check what the URL path is (like `/sse` or `/mcp`).
 
 <details>
-<summary>⚔️ Side Quest: What's the difference between <code>/mcp</code> and <code>/sse</code>?</summary>
+<summary>⚔️ <b>Side Quest</b>: What's the difference between <code>/mcp</code> and <code>/sse</code>?</summary>
 
-MCP currently defines two standard transport mechanisms:
+**MCP** currently defines two standard transport mechanisms:
 
 #### 🧠 `/mcp` – Standard Input/Output (stdio)
 
@@ -149,18 +145,19 @@ MCP currently defines two standard transport mechanisms:
 
 - **🛑 All other paths**
 ```ts
-return new Response("Not found", { status: 404 });
+return new Response("MCP server active 🤖. Connect via MCP protocol at /mcp or /sse.", { status: 404 });
 ```
-  - If the request doesn’t match /sse or /mcp, the server just replies with a “Not found” message.
+  - If the request doesn’t match `/sse` or `/mcp`, the server just replies with a 
+  **“MCP server active 🤖. Connect via MCP protocol at /sse or /mcp.”** message.
 
 
-If the request doesn’t match /sse or /mcp, the server just replies with a “Not found” message.
-
 ### 3. 📦 Install dependencies
 
-Install the required packages and start your MCP server so it can run locally and accept connections from your AI client.
+Install the required packages and start your MCP server so it can run locally and
+accept connections from your AI client. From the root of your repository:
 
 ```
+cd typescript/animal-rescue-mcp-server/src/
 npm install
 ```
 
@@ -170,11 +167,31 @@ npm install
 npm start
 ```
 
-You should see your MCP server booting up on <http://localhost:8787>
+You should see your MCP server booting up on <http://localhost:8787> with output similar to below.
+
+```
+> animal-rescue-mcp-server@0.0.0 start
+> wrangler dev
+
+
+ ⛅️ wrangler 4.22.0
+───────────────────
+Your Worker has access to the following bindings:
+Binding                     Resource            Mode
+env.MCP_OBJECT (MyMCP)      Durable Object      local
+
+╭──────────────────────────────────────────────────────────────────────╮
+│  [b] open a browser [d] open devtools [c] clear console [x] to exit  │
+╰──────────────────────────────────────────────────────────────────────╯
+[wrangler:info] Ready on http://localhost:8787
+```
+
+The server is now available for MCP connections 🥳
 
 ### 5. 🔌 Connect your MCP client (Choose ONE)
 
-Open your MCP-compatible client of choice and connect it to your running server:
+Open your MCP-compatible client of choice and connect it to your running server.
+In this exercise we are using Claude as the MCP client.:
 
 <details>
 <summary><strong>Claude Desktop</strong></summary>
@@ -198,14 +215,21 @@ Open your MCP-compatible client of choice and connect it to your running server:
   }
 }
 ```
-
 5. Restart Claude
 6. In the main window, tap on the “Search and tools” icon (next to the Plus icon). You should see your MCP server listed there.
 
-> Note: It may be currently disconnected, as there are no tools yet. We'll build them in the next step!
+<div align="center">
+  <img src="images/claude_animal_rescue-450x400.gif" alt="Connect your MCP Client">
+</div>
+
+> ℹ️ **Note**
+>
+> It may be currently disconnected, as there are no tools yet. We'll build them in the next step 😉!
+
 </details>
 
 
+
 <details>
 <summary><strong>Cloudflare Playground</strong></summary>
  
@@ -218,24 +242,30 @@ Open your MCP-compatible client of choice and connect it to your running server:
 
 At this point, if you try to connect to it, it may not work, as there are no tools available yet. We'll build them in the next step!
 
-#### MCP Inspector
+#### 🕵🏼‍♀️ MCP Inspector
+
+The [MCP Inspector][mcp-inspector] is an interactive developer tool for testing and debugging MCP servers.
 1. Run `npx @modelcontextprotocol/inspector` in a terminal
 2. Your browser should automatically open with the correct url, it will be printed out in the terminal as well
 3. Select transport type `sse` and url `http://localhost:8787/sse`
 
-> Note: there is no AI Agent invovled with MCP inspector, uses this when you want more direct visibility to the MCP Server (more info [here](https://modelcontextprotocol.io/docs/tools/inspector))
+> [!NOTE]
+> There is no AI Agent invovled with MCP inspector, uses this when you want more direct visibility to the MCP Server (more info [here](https://modelcontextprotocol.io/docs/tools/inspector))
 
 ⸻
 
 ### 6. 🧱 Understand the MCP Scaffolding
 
-Inside this class, we set up everything your AI-powered server needs — including:
+Next, we'll configure a [MCP tool][mcp-tool], which is how you expose specific functions to MCP clients
+so they can interact with your server's capabilities.
+To create a tool we use a class called **MyMCP**. Inside this class, described below,
+we set up everything your AI-powered server needs — including:
 
 * ✨ A name and version
 * 🧰 The tools it can call, which we will create in this workshop
 * 📄 Any resources it might return (like adoption info)
 
-Your setup might look like this:
+Your class setup might look like this:
 
 ```ts
 export class MyMCP extends McpAgent {
@@ -252,7 +282,7 @@ export class MyMCP extends McpAgent {
 }
 ```
 
-This structure keeps all your server logic tidy and makes it easy to add more tools or features as you go.
+This typescript structure keeps all your server logic tidy and makes it easy to add more tools or features as you go.
 
 ### 7. 🛠️ Add Tool 1: list_animals
 
@@ -267,11 +297,15 @@ This tool connects your MCP server to your animal data and makes it available to
 
 🧠 Where Do I Add This?
 
-Add this inside your `init()` method in your MyMCP class (in `index.ts` - which is where all your tools will be added).
+Add this inside your `init()` method of your MyMCP class. This class is defined in the `index.ts`,
+which is where all your tools will be added. 
+
+> [!NOTE]
+> This file is located under the `mcp-server-workshop/typescript/animal-rescue-mcp-server/src` folder
 
 Look for `// Tool 1: list_animals`
 
-Start typing out the `registerTool()` call inside init():
+Start typing out the `registerTool()` call inside `init()`:
 
 ```ts
 this.server.registerTool(
@@ -286,8 +320,8 @@ this.server.registerTool(
   // We’ll add what the tool does in the next step — it will return a list of animals as plain text
 );
 ```
-
-ℹ️ The tool name `list_animals` is how your mcp client will refer to it internally.
+> [!IMPORTANT]
+> The tool name `list_animals` is how your **MCP client** will refer to it internally.
 
 **Let's fill in the description where it currently says `TODO`.**
 
@@ -296,9 +330,9 @@ Tool descriptions are important, it's like **SEO for your tool** - the better yo
 **🤔 What did you come up with for your tool description?**
 
 <details>
-<summary>⚔ Side Quest: Writing Good Tool Descriptions</summary>
+<summary>⚔ <b>Side Quest</b>: Writing Good Tool Descriptions ✍🏼</summary>
 
-Picking the right description for your tool helps your mcp client know when (and how) to use it. This isn’t just documentation — it’s **part of the prompt**.
+Picking the right description for your tool helps your MCP client know when (and how) to use it. This isn’t just documentation — it’s **part of the prompt**.
 
 ---
 
@@ -326,36 +360,37 @@ Picking the right description for your tool helps your mcp client know when (and
 
 ---
 
-#### 💡 Tips
-
-* Use **clear verbs**: list, return, mark, suggest, look up  
-
-* Think: “How would I describe this tool in one sentence to another human?”
-* The model sees this — so make it *mcp-client-friendly*, not just code-friendly
+> 💡 Tip
+> * Use **clear verbs**: list, return, mark, suggest, look up  
+> * Think: “How would I describe this tool in one sentence to another human?”
+> * The model sees this — so make it *mcp-client-friendly*, not just code-friendly
 
 </details>
 <br>
 
-**Now let’s tell the tool what to do when your mcp client calls it.**
+**Now let’s tell the tool what to do when your MCP client calls it.**
 
 In this case, we want to return the full list of animals from your service as a plain text string.
 
 Here’s what that looks like:
 
 ```ts
-async () => ({
-  content: [{
-    type: "text",
-    text: JSON.stringify(this.animalRescueService.listAnimals())
-  }]
-})
+    async () => {
+      const animals = await this.animalRescueService.listAnimals();
+      return {
+        content: [{
+          type: "text",
+          text: JSON.stringify({ animals })
+        }]
+      };
+    }
 ```
 
 This will:
 
 * Call your pre-built function `listAnimals()`
-* Convert the result into a readable JSON string
-* Return it as plain text, which your mcp client can read and use in its reply
+* Convert the result into a readable **JSON string**
+* Return it as plain text, which your **MCP client** can read and use in its reply
 
 Paste that into your code where the following comment appears:
 
@@ -363,7 +398,7 @@ Paste that into your code where the following comment appears:
 
 <details>
 
-<summary>🆘 Break Glass Code: Copy/paste version of list_animals</summary>
+<summary>🆘 <b>Break Glass Code:</b> Copy/paste version of list_animals</summary>
 
 ```ts
 async init() {
@@ -402,6 +437,10 @@ Can you list all the animals available for adoption?
 
 Claude should call your tool and reply with a list of pets! 🎉
 
+<div align="center">
+  <img src="images/claude_list_animals_tool-450x400.gif" alt="List animal tool">
+</div>
+
 <details>
 <summary>🐞 Common Errors + Debugging Tips</summary>
 
@@ -414,6 +453,8 @@ Claude should call your tool and reply with a list of pets! 🎉
 
 </details>
 
-Nice work on getting this far. Now that we've created our first tool, let's imbed that knowledge further and creation some more tools in Part 2!
+Nice work on getting this far 🙌🏼🥳🍾🎈. Now that we've created our first tool, let's imbed that knowledge further and creation some more tools in [Part 2](part-2-instructions.md)!
+
 
-## [Part 2](part-2-instructions.md)
+[mcp-inspector]: https://modelcontextprotocol.io/legacy/tools/inspector
+[mcp-tool]: https://modelcontextprotocol.io/specification/2025-06-18/server/tools
\ No newline at end of file
diff --git a/typescript/animal-rescue-mcp-server/src/index.ts b/typescript/animal-rescue-mcp-server/src/index.ts
index 133764f..4d436fb 100644
--- a/typescript/animal-rescue-mcp-server/src/index.ts
+++ b/typescript/animal-rescue-mcp-server/src/index.ts
@@ -51,6 +51,6 @@ export default {
 				.fetch(request, env, ctx);
 		}
 
-		return new Response("Not found", { status: 404 });
+		return new Response("MCP server active 🤖. Connect via MCP protocol at /mcp or /sse.", { status: 404 });
 	},
 };