updated draft

Author: TuannasCodeCatastrophe

app/_how-tos/use-insomnia-mcp-clients-to-test-aggregated-mcp-tools.md

@@ -49,76 +49,45 @@ prereqs:
 tldr:
   q: How do I test aggregated MCP tools using Insomnia?
   a: |
-    Connect an Insomnia MCP client to the listener-mode AI MCP Proxy endpoint created during the aggregation setup. Then invoke each tool and validate behaviour using Insomnia’s Params, Headers, Events, and Console panels.
+    Connect an Insomnia MCP client to the listener-mode AI MCP Proxy endpoint that the aggregation setup creates. Then test each tool and validate behaviour using Insomnia’s Params, Headers, Events, and Console panels.
 ---
 
 Use Insomnia to connect to an MCP server exposed through the AI MCP Proxy plugin in listener mode. 
 
 This listener server aggregates MCP tools from multiple upstream APIs, enabling you to validate end-to-end behaviour using Insomnia’s Params, Headers, Events, and Console panels.
 
-After completing the aggregation workflow described in **[Aggregate MCP tools from multiple AI MCP Proxy plugins](/mcp/aggregate-mcp-tools/)** and exposing an autogenerated or aggregated MCP server, follow this guide to test and validate its MCP tools using Insomnia’s MCP Clients:
+After completing the aggregation workflow described in **[Aggregate MCP tools from multiple AI MCP Proxy plugins](/mcp/aggregate-mcp-tools/)** and exposing an autogenerated or aggregated MCP server, follow this guide to test and validate its MCP tools using Insomnia’s MCP Clients.
 
 ## Create an MCP client
 
 1. Open **Insomnia**.
-2. In the left sidebar, click **MCP Clients**.
+2. In the sidebar, click **MCP Clients**.
 3. Click **New MCP Client**.
-4. In the **Name** field, enter a name:
-       Aggregated MCP Tools
-5. In the **MCP Server URL** field, enter your listener URL:
-       http://localhost:8000/mcp-listener
+4. In the **Name** field, enter a name: **Aggregated MCP Tools**
+5. In the **MCP Server URL** field, enter your listener URL: `http://localhost:8000/mcp-listener`
 6. Click **Connect**.
 
-Insomnia connects to the MCP server and discovers all aggregated tools.
+Insomnia connects to the MCP server and discovers all of the aggregated tools.
 
-## Validate discovered tools
+## Validate tools
 
-1. In toolbar, locate the **Tools** drop-down section.
-2. Review the list of available tools.  
+1. In the sidebar, locate the **Tools** drop-down section.
+2. Review the list of available tools.
 
-If any tools are missing:
-
-- Confirm all conversion-only plugins use the same `tags[]` value.
+{:.info}
+> If any tools are missing:
+- Confirm that all conversion-only plugins use the same `tags[]` value.
 - Confirm that the listener-mode plugin’s `server.tag` matches that value.
 - Confirm that the listener Route is active and reachable.
 
-## Invoke and test tools
+## Test tools
 
-Use Insomnia’s testing panels to validate MCP tool behaviour. Complete the following process to run a tool:
+Use Insomnia’s testing panels to validate MCP tool behaviour:
 
 1. In **Tools**, click any tool.
-2. Click the **Params** tab.
-3. Enter parameter values.
+2. In the request pane, click the **Params** tab.
+3. Enter the required parameter value.
 4. Click **Call Tool**.
-5. Click the **Console** tab.
-
-## Debug tool behaviour using Insomnia panels
-
-Insomnia provides several panels to validate MCP activity:
-
-- **Params**: Verify the parameters passed to the tool.  
-- **Headers (Request)**: Inspect headers added by plugins such as Request Transformer Advanced.  
-- **Headers (Response)**: Validate response headers and status.  
-- **Events**: View lifecycle and authentication events.  
-- **Console**: Inspect raw MCP JSON-RPC requests and responses.
-
-Use these panels to confirm:
-
-- Correct parameter mapping  
-- Correct API key injection (if configured)  
-- Upstream connectivity  
-- Schema-correct JSON responses  
-
-
-## Validate aggregated MCP behaviour end-to-end
-
-1. Select any tool.
-2. Click **Call Tool**.
-3. Open the **Console** tab.
-4. Confirm:
-   - The MCP request structure is valid  
-   - The listener-mode MCP Proxy plugin processes the request  
-   - The upstream service responds successfully  
-   - The returned JSON matches the tool’s schema  
+5. In the response pane, click the **Console** tab. 
 
 A successful response confirms that your aggregated MCP configuration is working correctly.