Update README files (#71)

Author: gspencergoog

README.md

@@ -49,6 +49,16 @@ The new commands will be available in new Gemini CLI sessions. The following com
 - `/modify` - Manages a structured modification session with automated planning.
 - `/commit` - Automates pre-commit checks and generates a descriptive commit message.
 
+### 3. Available Tools
+
+This extension also installs an MCP server (`flutter_launcher`) that provides tools for starting, stopping, and interacting with Flutter applications. This server is started automatically, and the following tools are made available:
+
+- `launch_app`: Launches a Flutter application on a specified device.
+- `stop_app`: Stops a running Flutter application.
+- `list_devices`: Lists all available devices that can run Flutter applications.
+- `get_app_logs`: Retrieves the logs from a running Flutter application.
+- `list_running_apps`: Lists all Flutter applications currently running that were started by this extension.
+
 ## 💡 Usage
 
 This extension provides powerful commands to automate key phases of the development lifecycle.

flutter_launcher_mcp/README.md

@@ -47,7 +47,6 @@ The server exposes the following tools:
 
 Launches a Flutter application with specified arguments and returns its DTD URI and process ID.
 
-- **Description:** Launches a Flutter application and returns its DTD URI.
 - **Input Schema:**
 
   ```json
@@ -60,11 +59,11 @@ Launches a Flutter application with specified arguments and returns its DTD URI
       },
       "target": {
         "type": "string",
-        "description": "The main entry point file of the application."
+        "description": "The main entry point file of the application. Defaults to \"lib/main.dart\"."
       },
       "device": {
         "type": "string",
-        "description": "The device ID to launch the application on."
+        "description": "The device ID to launch the application on. To get a list of available devices to present as choices, use the list_devices tool."
       }
     },
     "required": ["root", "device"]
@@ -90,34 +89,10 @@ Launches a Flutter application with specified arguments and returns its DTD URI
   }
   ```
 
-- **Example Call (Conceptual):**
-
-  ```dart
-  // Assuming 'client' is an initialized ServerConnection from dart_mcp
-  final launchResult = await client.callTool(
-    CallToolRequest(
-      name: 'launch_app',
-      arguments: {
-        'root': '/path/to/your/flutter/project',
-        'device': 'emulator-5554',
-      },
-    ),
-  );
-
-  if (!launchResult.isError) {
-    final dtdUri = launchResult.structuredContent!['dtdUri'] as String;
-    final pid = launchResult.structuredContent!['pid'] as int;
-    print('Flutter app launched! DTD URI: $dtdUri, PID: $pid');
-  } else {
-    print('Failed to launch Flutter app: ${launchResult.content.first.text}');
-  }
-  ```
-
 #### `stop_app`
 
-Kills a running Flutter process managed by this server.
+Kills a running Flutter process started by the `launch_app` tool.
 
-- **Description:** Kills a running Flutter process managed by this server.
 - **Input Schema:**
 
   ```json
@@ -148,23 +123,111 @@ Kills a running Flutter process managed by this server.
   }
   ```
 
-- **Example Call (Conceptual):**
-
-  ```dart
-  // Assuming 'client' is an initialized ServerConnection from dart_mcp
-  // and 'launchedPid' is the PID obtained from a previous launchFlutter call
-  final killResult = await client.callTool(
-    CallToolRequest(
-      name: 'stop_app',
-      arguments: {'pid': launchedPid},
-    ),
-  );
-
-  if (!killResult.isError) {
-    final success = killResult.structuredContent!['success'] as bool;
-    print('Kill process result: $success');
-  } else {
-    print('Failed to kill process: ${killResult.content.first.text}');
+#### `list_devices`
+
+Lists available Flutter devices.
+
+- **Input Schema:**
+
+  ```json
+  {
+    "type": "object"
+  }
+  ```
+
+- **Output Schema:**
+
+  ```json
+  {
+    "type": "object",
+    "properties": {
+      "devices": {
+        "type": "array",
+        "description": "A list of available device IDs.",
+        "items": {
+          "type": "string"
+        }
+      }
+    },
+    "required": ["devices"]
+  }
+  ```
+
+#### `get_app_logs`
+
+Returns the collected logs for a given flutter run process id. Can only retrieve logs started by the `launch_app` tool.
+
+- **Input Schema:**
+
+  ```json
+  {
+    "type": "object",
+    "properties": {
+      "pid": {
+        "type": "integer",
+        "description": "The process ID of the flutter run process running the application."
+      }
+    },
+    "required": ["pid"]
+  }
+  ```
+
+- **Output Schema:**
+
+  ```json
+  {
+    "type": "object",
+    "properties": {
+      "logs": {
+        "type": "array",
+        "description": "The collected logs for the process.",
+        "items": {
+          "type": "string"
+        }
+      }
+    },
+    "required": ["logs"]
+  }
+  ```
+
+#### `list_running_apps`
+
+Returns the list of running app process IDs and associated DTD URIs for apps started by the `launch_app` tool.
+
+- **Input Schema:**
+
+  ```json
+  {
+    "type": "object"
+  }
+  ```
+
+- **Output Schema:**
+
+  ```json
+  {
+    "type": "object",
+    "properties": {
+      "apps": {
+        "type": "array",
+        "description": "A list of running applications started by the launch_app tool.",
+        "items": {
+          "type": "object",
+          "properties": {
+            "pid": {
+              "type": "integer",
+              "description": "The process ID of the application."
+            },
+            "dtdUri": {
+              "type": "string",
+              "description": "The DTD URI of the application."
+            }
+          },
+          "required": ["pid", "dtdUri"]
+        }
+      }
+    },
+    "required": ["apps"]
   }
   ```